Are you sure you want to cancel your subscription?

If you cancel, your subscription will remain active through the paid term. You will be able to reactivate the subscription until that date.

Sorry to see you go

Your subscription will remain active until . If you change your mind, you may rectivate your subscription anytime before that date.

Are you sure you want to reactivate?
Welcome Back!

Your subscription has been reactivated and you will continue to be charged on .

Reactivate Subscription

Thank you for choosing to reactivate your subscription. In order to lock in your previous subscription rate, you owe: .

Your Subscription term is from - .

Questions? Call Sales.

Payment Due:

Auto-Renew Subscription

To auto-renew your subscription you need to select or enter your payment method in "Your Account" under Manage Payments.

Click continue to set up your payments.

CBT Nuggets License Agreement

Unless otherwise stated all references to “training videos” or to “videos” includes both individual videos within a series, entire series, series packages, and streaming subscription access to CBT Nuggets content. All references to CBT or CBT Nuggets shall mean CBT Nuggets LLC, a Delaware limited liability company located at 44 Country Club Road, Ste. 150, Eugene, Oregon.

A CBT Nuggets license is defined as a single user license. Accounts may purchase multiple users, and each user is assigned a single license.

  • GRANT OF LICENSE. CBT Nuggets grants you a non-transferable, non-exclusive license to use the training videos contained in this package or streaming subscription access to CBT content (the “Products”), solely for internal use by your business or for your own personal use. You may not copy, reproduce, reverse engineer, translate, port, modify or make derivative works of the Products without the express consent of CBT. You may not rent, disclose, publish, sell, assign, lease, sublicense, market, or transfer the Products or use them in any manner not expressly authorized by this Agreement without the express consent of CBT. You shall not derive or attempt to derive the source code, source files or structure of all or any portion of the Products by reverse engineering, disassembly, decompilation or any other means. You do not receive any, and CBT Nuggets retains all, ownership rights in the Products. The Products are copyrighted and may not be copied, distributed or reproduced in any form, in whole or in part even if modified or merged with other Products. You shall not alter or remove any copyright notice or proprietary legend contained in or on the Products.
  • TERMINATION OF LICENSE. Once any applicable subscription period has concluded, the license granted by this Agreement shall immediately terminate and you shall have no further right to access, review or use in any manner any CBT Nuggets content. CBT reserves the right to terminate your subscription if, at its sole discretion, CBT believes you are in violation of this Agreement. CBT reserves the right to terminate your subscription if, at its sole discretion, CBT believes you have exceeded reasonable usage. In these events no refund will be made of any amounts previously paid to CBT.
  • DISCLAIMER OF WARRANTY AND LIABILITY. The products are provided to you on an “as is” and “with all faults” basis. You assume the entire risk of loss in using the products. The products are complex and may contain some nonconformities, defects or errors. CBT Nuggets does not warrant that the products will meet your needs, “expectations or intended use,” that operations of the products will be error-free or uninterrupted, or that all nonconformities can or will be corrected. CBT Nuggets makes and user receives no warranty, whether express or implied, and all warranties of merchantability, title, and fitness for any particular purpose are expressly excluded. In no event shall CBT Nuggets be liable to you or any third party for any damages, claim or loss incurred (including, without limitation, compensatory, incidental, indirect, special, consequential or exemplary damages, lost profits, lost sales or business, expenditures, investments, or commitments in connection with any business, loss of any goodwill, or damages resulting from lost data or inability to use data) irrespective of whether CBT Nuggets has been informed of, knew of, or should have known of the likelihood of such damages. This limitation applies to all causes of action in the aggregate including without limitation breach of contract, breach of warranty, negligence, strict liability, misrepresentation, and other torts. In no event shall CBT Nuggets’ liability to you or any third party exceed $100.00.
  • REMEDIES. In the event of any breach of the terms of the Agreement CBT reserves the right to seek and recover damages for such breach, including but not limited to damages for copyright infringement and for unauthorized use of CBT content. CBT also reserves the right to seek and obtain injunctive relief in addition to all other remedies at law or in equity.
  • MISCELLANEOUS. This is the exclusive Agreement between CBT Nuggets and you regarding its subject matter. You may not assign any part of this Agreement without CBT Nuggets’ prior written consent. This Agreement shall be governed by the laws of the State of Oregon and venue of any legal proceeding shall be in Lane County, Oregon. In any proceeding to enforce or interpret this Agreement, the prevailing party shall be entitled to recover from the losing party reasonable attorney fees, costs and expenses incurred by the prevailing party before and at any trial, arbitration, bankruptcy or other proceeding and in any appeal or review. You shall pay any sales tax, use tax, excise, duty or any other form of tax relating to the Products or transactions. If any provision of this Agreement is declared invalid or unenforceable, the remaining provisions of this Agreement shall remain in effect. Any notice to CBT under this Agreement shall be delivered by U.S. certified mail, return receipt requested, or by overnight courier to CBT Nuggets at the following address: 44 Club Rd Suite 150, Eugene, OR 97401 or such other address as CBT may designate.

CBT Nuggets reserves the right, in its sole discretion, to change, modify, add, or remove all or part of the License Agreement at any time, with or without notice.

Billing Agreement

  • By entering into a Billing Agreement with CBT Nuggets, you authorize CBT Nuggets to use automatic billing and to charge your credit card on a recurring basis.
  • You agree to pay subscription charges on a monthly basis, under the following terms and conditions:
    • CBT Nuggets will periodically charge your credit card each monthly billing cycle as your subscription charges become due;
    • All payments are non-refundable and charges made to the credit card under this agreement will constitute in effect a "sales receipt" and confirmation that services were rendered and received;
    • To terminate the recurring billing process and/or arrange for an alternative method of payment, you must notify CBT Nuggets at least 24 hours prior to the end of the monthly billing cycle;
    • You will not dispute CBT Nugget’s recurring billing charges with your credit card issuer so long as the amount in question was for periods prior to the receipt and acknowledgement of a written request to cancel your account or cancel individual licenses on your account.
  • You guarantee and warrant that you are the legal cardholder for the credit card associated with the account, and that you are legally authorized to enter into this recurring billing agreement.
  • You agree to indemnify, defend and hold CBT Nuggets harmless, against any liability pursuant to this authorization.
  • You agree that CBT Nuggets is not obligated to verify or confirm the amount for the purpose of processing these types of payments. You acknowledge and agree that Recurring Payments may be variable and scheduled to occur at certain times.
  • If your payment requires a currency conversion by us, the amount of the currency conversion fee will be determined at the time of your payment. You acknowledge that the exchange rate determined at the time of each payment transaction will differ and you agree to the future execution of payments being based on fluctuating exchange rates.

CBT Nuggets reserves the right, in its sole discretion, to change, modify, add, or remove all or part of the Billing Agreement at any time, with or without notice.

Cisco CCNP TSHOOT 642-832

Switch TSHOOT: VLANs and Spanning Tree Concept Review

This video is only available to subscribers.
Start your 7-day free trial today.

A free trial includes:

  • Unlimited 24/7 access to our entire IT training video library.
  • Ability to train on the go with our mobile website and iOS/Android apps.
  • Note-taking, bookmarking, speed control, and closed captioning features.
Video Titles Duration
1. TSHOOT: Setting Your Expectations
2. General TSHOOT: The Troubleshooting State of Mind
3. General TSHOOT: Troubleshooting Before You're Treading Water - Proactive Steps
4. General TSHOOT: Troubleshooting Before You're Treading Water - Proactive Steps, Part 2
5. General TSHOOT: IOS Tools to Monitor and Maintain the Network
6. General TSHOOT: IOS Tools to Monitor and Maintain the Network, Part 2
7. Switch TSHOOT: VLANs and Spanning Tree Concept Review
8. Switch TSHOOT: VLANs and Spanning Tree
9. Switch TSHOOT: VLANs and Spanning Tree, Part 2
10. Switch TSHOOT: L3 Switching and Redundancy Protocols Concept Review
11. Switch TSHOOT: L3 Switching and Redundancy Protocols
12. Switch TSHOOT: L3 Switching and Redundancy Protocols, Part 2
13. Route TSHOOT: L3 Connectivity and EIGRP Concept Review
14. Route TSHOOT: L3 Connectivity and EIGRP
15. Route TSHOOT: L3 Connectivity and EIGRP, Part 2
16. Route TSHOOT: L3 Connectivity and EIGRP, Part 3
17. Route TSHOOT: OSPF and Route Redistribution Concept Review
18. Route TSHOOT: OSPF and Route Redistribution
19. Route TSHOOT: OSPF and Route Redistribution, Part 2
20. Route TSHOOT: BGP Concept Review
21. Route TSHOOT: BGP
22. Route TSHOOT: Router Performance Issues Concept Review
23. Route TSHOOT: Router Performance Issues
24. Security TSHOOT: Access List Concept Review
25. Security TSHOOT: Access List Chaos
26. IPv6 TSHOOT: IPv6 and IPv6 Routing Protocols

TSHOOT: Setting Your Expectations

General TSHOOT: The Troubleshooting State of Mind

General TSHOOT: Troubleshooting Before You're Treading Water - Proactive Steps

General TSHOOT: Troubleshooting Before You're Treading Water - Proactive Steps, Part 2

General TSHOOT: IOS Tools to Monitor and Maintain the Network

General TSHOOT: IOS Tools to Monitor and Maintain the Network, Part 2

Switch TSHOOT: VLANs and Spanning Tree Concept Review

00:00:00 - OK. It's time to get into the actual technical material. But
00:00:05 - before we get into the troubleshooting itself, for each one of
00:00:09 - these concepts, I'm going to do a little bit of review. The first
00:00:12 - one of these is going to be focused on VLANs and Spanning-Tree.
00:00:15 - So we're going to do a brief concept review of each one of these,
00:00:18 - you can see VLANs and Spanning-Tree, and then talk about just
00:00:21 - some key troubleshooting commands that can help you out along
00:00:24 - the way.
00:00:25 - Let's start off talking about VLANs. VLANs are still, to this
00:00:30 - day, one of my favorite things to talk about, especially when
00:00:33 - you get to the CCNA person who comes in and is a little kind
00:00:38 - of fuzzy as to what a VLAN even is. The fun part is everybody
00:00:41 - has heard of it. It's like subnetting. Everybody has heard of
00:00:44 - subnetting. They kind of have that nervous fear of it. It always
00:00:49 - goes like this. I ask a class, "OK. How many of you have heard
00:00:54 - of VLANs?" and almost every hand goes up. They're, "Oh, I've
00:00:57 - heard. Oh yes, we use it. We use VLANs. VLANs are everywhere."
00:01:00 - It's kind of like this kind of popcorn response. I go, "Yes,
00:01:03 - yes, yes. Well, let me tell you what it is." And I just go to
00:01:07 - the board and I just draw a simple little, there is a switch.
00:01:11 - You bought it at Best Buy for 15 bucks. Actually, a little more
00:01:15 - than that if it supports VLANs. But it's a four-port switch,
00:01:19 - and if I break it into VLANs, let's say I put the two ports on
00:01:22 - the left into one VLAN and the two ports on the right on another
00:01:25 - VLAN, it's as if I took that switch over my knee and went, "Aah,
00:01:28 - snap!" and broke it in half, and everybody goes, "Oooh!" And
00:01:31 - now I've got two working switches. That's what a VLAN is. It
00:01:35 - actually totally breaks apart the different pieces of the network.
00:01:38 - And everybody, "Oh." I'm telling you that that's one of those
00:01:41 - things that just resonates with everybody. They get it. And then
00:01:43 - I expand out and I say, "OK. Well, a VLAN, when you do that,
00:01:48 - as if they're in their own logical group, a broadcast within
00:01:51 - a VLAN stays in a VLAN. They've got their own IT subnet." And
00:01:54 - of course, you start expanding on all these terms because these
00:01:57 - are CCNA people. You don't want to melt them. But here I'm talking
00:02:00 - to you at the end of the TSHOOT series, or into the TSHOOT series,
00:02:04 - I should say, at the end of the CCNP track, and you guys got
00:02:08 - this to where this is what VLANs are all about. You can put security
00:02:11 - boundaries. I mean what network doesn't use VLANs? You know what
00:02:16 - they're all about. So VLANs can transcend switches through trunk
00:02:21 - ports, which is a Cisco word. Every other vendor calls them a
00:02:25 - tagged port, and I like that word better because it reflects
00:02:28 - what they do, which is they keep the 802.1Q
00:02:32 - tagged on there, which is the only industry-standard tagging
00:02:36 - language, ISL is dead, and that tag stays on there. And so if
00:02:40 - this guy sends a broadcast, that's how all these other switches
00:02:43 - know, "Oh, you're sending a broadcast. It belongs to the red
00:02:46 - VLAN. I got it," and that goes to all the right ports. You can
00:02:49 - have up to 4,096 VLANs, although not every switch supports that
00:02:54 - many active VLANs. They should all support those VLAN numbers.
00:02:59 - VTP, which is the VLAN Trunking Protocol, should have been called
00:03:04 - the VLAN Replication Protocol. Cisco is really trying to steer
00:03:08 - away from this nowadays because the best practice says you should
00:03:11 - not create VLANs on switches where they don't belong. Whereas
00:03:14 - VTP replicates all your VLANs to all the different switches in
00:03:18 - the organization, whether it belongs there or not. Now
00:03:21 - speaking of best practices, everything is changed in recent years,
00:03:25 - as you probably have seen, and no longer is it considered a good
00:03:28 - practice to have VLANs spanning the entire organization. It used
00:03:32 - to be, let's say this was company let me put
00:03:38 - my pen on the right Layer here this is company A. It used to
00:03:42 - be that you could have VLAN 10 and VLAN 10 would go campus-wide.
00:03:45 - No matter where you were in that campus, if you were in VLAN
00:03:49 - 10, you were on the same subnet. It works well for things like
00:03:51 - wireless, for voice over IP, like span the entire campus. It
00:03:55 - was great. Nowadays, Cisco says you can't do that or you shouldn't
00:03:59 - do that. Nowadays, Cisco says you should be using something called
00:04:03 - local VLANs. And that's where VLANs are constrained to a wiring
00:04:07 - closet, to where, let's say this is building A and you have this
00:04:11 - wiring closet with a couple Layer of three switches, a couple
00:04:14 - access Layer switches and then your clients. VLAN 10 should stay
00:04:18 - within this block. It should not move across these, and the main
00:04:22 - reason for that is because Cisco now recommends Layer 3 everywhere.
00:04:26 - You've got Layer 3 from your distribution Layer switches to your
00:04:30 - core Layer, so that's a point-to-point link. You've got Layer
00:04:33 - 3 between, well, if you can do it, between your distribution
00:04:37 - Layer and your access Layer even to where literally, you've got
00:04:41 - point-to-point LAN we'll call them LAN links everywhere because
00:04:45 - now you can use routing protocols rather than Spanning-Tree to
00:04:49 - converge. And routing protocols can always be faster than Spanning-Tree
00:04:53 - could. So that moves you into this local VLAN design to where
00:04:58 - VLANs are now constrained into the wiring closet.
00:05:03 - Doing these reviews are kind of funny because I'm thinking, "How
00:05:07 - can I explain everything about VLANs in five minutes or less?"
00:05:11 - I mean the good news is I know I'm preaching to the choir. You
00:05:14 - guys know what VLANs are all about. So let me talk a little bit
00:05:18 - about some key troubleshooting commands kind of a mindset when
00:05:22 - you're troubleshooting VLANs. The beauty of VLANs is it's primarily
00:05:26 - Layer 2 and below. So when you're thinking about things, you're
00:05:29 - doing commands like "show mac-address-table" to see what MAC
00:05:33 - addresses have been learned on a port, what VLAN they are associated
00:05:36 - with. You're doing a "show vlan" which shows all of the VLANs
00:05:40 - that are created on the switch and what ports have been assigned
00:05:45 - to the specific VLANs. I'm telling you, when I was troubleshooting
00:05:48 - VLANs, that's one of the first commands I type. Give me a list
00:05:51 - of the VLANs because it's one thing to have the port assigned
00:05:53 - to it and it's another thing for the VLAN to actually exist.
00:05:57 - I can't tell you how many times I'm troubleshooting something,
00:06:00 - a computer has no connectivity, and I don't actually have physical
00:06:03 - access to the switch so I can't see the amber light blinking
00:06:07 - above the port, but I'm going, "What's the deal? What's the deal?"
00:06:10 - and I find out that this port has been made a member of a VLAN
00:06:15 - that actually has not been added to that switch. And the weird
00:06:18 - thing is the port just disappears. I mean it doesn't show up.
00:06:23 - When you do "show vlan," it's not listed there. It's in the running
00:06:26 - config, sure, but if the VLAN doesn't exist, then it says that
00:06:30 - the Layer 2 fabric that the computer sits on is gone, that the
00:06:35 - little blanket that it's sitting on has been whisked out from
00:06:39 - underneath so it can't talk to anything. So the "show vlan" command
00:06:42 - shows both of those things: the VLAN has been created and that
00:06:46 - the port has been assigned. "Show interface switchboard," this
00:06:50 - one is really useful for finding out trunk ports, for example,
00:06:56 - especially you want to find out which ports are configured in
00:06:59 - that dynamic mode, that mode that we all love to hate, the dynamic
00:07:03 - mode where it flips between access and trunk that will show which
00:07:05 - ones are dynamic mode. It will show trunk ports. It will show
00:07:08 - what ports are going to cross there. A matter of fact, let me
00:07:11 - jump on here real quick. For trunk ports, I love this one, "show
00:07:15 - interface trunk" allows you to see which interfaces
00:07:20 - are configured as trunk ports as well as what VLANs they are
00:07:24 - affording. So if for instance, if you have chosen to restrict
00:07:27 - what VLANs go across the trunk interface, which is a good practice,
00:07:31 - you're able to see that information right here. So maybe a VLAN
00:07:35 - is not working as you would expect on a switch. You want to make
00:07:38 - sure that it's been added to the trunk port on both sides and
00:07:41 - that's a great command to do it right there. This is a little
00:07:44 - known command and I've actually only used this once or twice
00:07:47 - in the real world, but it's very handy when you do: traceroute
00:07:53 - MAC. You guys know what a traceroute is, right, to where I'm
00:07:56 - sitting at a PC and I want to find out what routers I'm going
00:07:59 - through on the way to You can actually do a trace
00:08:02 - and it will show you every hop. Well, traceroute MAC is something
00:08:05 - that's supported on Cisco switches, and I emphasize that because
00:08:09 - it relies on the Cisco Discovery Protocol. If I have a bunch
00:08:13 - of switches daisy chained together and I want to know what switches
00:08:18 - I'm going through to reach a specific MAC address, that's where
00:08:22 - this comes in. Pretty sweet, huh? So that's a great way to kind
00:08:26 - of do a trace through your Layer 2 infrastructure. Again, the
00:08:29 - only requirement is that all those switches in that chain have
00:08:32 - CDP enabled. Now I know everybody is like, "Well, isn't CDP
00:08:37 - a bad security practice?"
00:08:39 - I don't know. I've got to be honest. If you read Cisco documentation,
00:08:45 - you'll find one document that's saying, "Yes, turn off CDP. You
00:08:48 - don't want people finding out about CDP blah, blah, blah." But
00:08:52 - then you'll find another document that says, "Oh yes, leave CDP
00:08:54 - on. It's not a bad deal." And a matter of fact, nowadays, it's
00:08:58 - recommended to turn it on on any interface that's connecting
00:09:01 - to an IP phone because it's useful for negotiating power requirements
00:09:04 - and transmitting voice VLAN information. I mean there is a lot
00:09:07 - that CDP can do. So I will be honest, I totally leave it on everywhere
00:09:13 - in the company. It's just it's too handy of a protocol to turn
00:09:16 - off. But that being said, you may end up with a security auditor
00:09:20 - coming in saying, "Hey, CDP, bad practice." Whatever. So do what
00:09:24 - your organization's security requirements and policies have told
00:09:28 - you to. So
00:09:29 - now let's move into my fly-by review of Spanning-Tree, probably
00:09:33 - one of the toughest concepts for the entry level person to get.
00:09:38 - And I always tell people, again, I talk about how do I teach
00:09:42 - this at the CCNA level. When I get to Spanning-Tree, I am head
00:09:46 - honest. I say this is one of the toughest concepts for me to
00:09:49 - teach, and I always emphasize it's not because the concept is
00:09:53 - complex. I mean it kind of is, but I mean if you think about
00:09:57 - it, Spanning-Tree, it's so simple. You're going, "What's up with
00:10:01 - the tree?" Well, that's the whole concept, right? All Spanning-Tree
00:10:04 - does is find, "Oh, looks like there is a redundant link that
00:10:08 - could cause a broadcast storm. Boom. Let's drop a tree on it."
00:10:13 - That's Spanning-Tree and you've got this little gap here now.
00:10:15 - It breaks the link. It brings that continuity to where you don't
00:10:18 - have the loop in the network. That is Spanning-Tree in all its
00:10:21 - glory. And I always say that's why it's the toughest concept
00:10:24 - for me to teach is because that's all there is to it, but now
00:10:27 - we're going to talk about that for hours because this is not
00:10:31 - what your networks look like. You don't have a network with two
00:10:34 - switches connected with a redundant link. You have a network
00:10:37 - that has 50 switches, and this one connects to this one and this
00:10:40 - one connects to this one and that one connects to that one and
00:10:41 - that one loops back here and this one connects over here. And
00:10:44 - then you have to say, "OK. Well, how does Spanning-Tree stop
00:10:46 - that? Well, why did it block that link? Why did it choose not
00:10:49 - to block that link?" And then people go, "Oh, OK. That's why
00:10:52 - it's so complex." And I kind of, I will be dead honest with you,
00:10:56 - I hate teaching Spanning-Tree just because it's so full of just,
00:11:00 - like, boring details and, "Oh, here is what a BPDU is. And I
00:11:05 - know some of you are, like, "Well, BPDUs are important." Totally.
00:11:07 - I totally bond with you. BPDUs are important. It's Rapid Spanning-Tree.
00:11:12 - It is important. Root bridges are important but it's just concept
00:11:16 - after concept after concept that it's all focused on just blocking
00:11:19 - that link and it's just because our networks are so complex,
00:11:23 - we need all of these complex concepts for it. One of the big
00:11:28 - things you want to remember about Spanning-Tree is that there
00:11:31 - are multiple flavors of it. And I don't know if this is real,
00:11:35 - it would freak me out if it is, but these flavors of Pringles,
00:11:38 - I know there is, like, every flavor of Pringle under the sun.
00:11:40 - Matter of fact, I got Seven-Layer Taco Dip Pringles not too long
00:11:44 - ago. They were really gross. But this is actually Soft-Shell
00:11:48 - Crab Pringles, Grilled Shrimp Pringles, and Seaweed Pringles.
00:11:53 - That would freak me out to see that in somebody's cabinet. But
00:11:58 - nonetheless, three flavors of Spanning-Tree. The original Spanning-Tree
00:12:02 - protocol, great at blocking loops but extremely slow by today's
00:12:07 - standards, up to 50 seconds to reconverge just because the link
00:12:12 - went down to find a new way to the root bridge. So Spanning-Tree,
00:12:16 - it is still alive and well and in networks everywhere, but I
00:12:20 - would say if it's in your production network, like data center,
00:12:23 - get it out. You want to move over to Rapid Spanning-Tree. Rapid
00:12:28 - Spanning-Tree, I would say fairly new in terms of the switch
00:12:33 - world. It's kind of funny. I was doing this indiscernible where
00:12:37 - I actually pulled the switch out of a customer network that we
00:12:40 - were just replacing. It was CatOS. It was just old. And I threw
00:12:44 - it up on my desk and I was looking at it, and I kind of blinked
00:12:47 - twice because I looked at the label and it actually said, right
00:12:50 - on it, I mean seriously, it was a 48-port it's still sitting
00:12:54 - in my garage CatOS switch. It was like, I want to say 2948.
00:12:58 - And right on the lower right-hand corner, it said 10/100/1000
00:13:04 - Ethernet. And I'm sitting there looking at it, and I go, "Seriously?
00:13:07 - That's a Gigabit switch? 48 ports of Gigabit?" And I sat there
00:13:10 - scratching my head. I powered up. Sure enough, it's Gigabit.
00:13:13 - And I'm thinking, "Now wait a second. That thing is running CatOS?
00:13:18 - Gigabit Ethernet?" I'm, like, "Has Gigabit Ethernet been out
00:13:20 - that long? I guess it has." And that's the thing, is I started
00:13:24 - thinking about why do we not run Rapid Spanning-Tree everywhere?
00:13:28 - Well, we still have 10/100 switches from a decade ago, I mean
00:13:32 - literally, 10 years ago, that are running just fine in people's
00:13:34 - network. They don't support Rapid Spanning-Tree but they're working
00:13:38 - fine. And to really run Rapid Spanning-Tree and get all the benefits,
00:13:41 - you got to run Rapid Spanning-Tree everywhere. So Rapid Spanning-Tree,
00:13:45 - the great thing about it is that it remembers the block link,
00:13:49 - whereas Spanning-Tree, let's say we've got our typical Spanning-Tree
00:13:51 - network right here, redundant link. This is the root bridge.
00:13:55 - This is our redundant link. Well, Spanning-Tree forgets about
00:13:58 - this, so if one of these links dies, it has to kind of rediscover
00:14:01 - that and put it through the blocking, listening, learning, and
00:14:04 - all of those process. Whereas Rapid Spanning-Tree goes, OK, I
00:14:07 - blocked that link but I'm marking it as a redundant backup link.
00:14:11 - And should something terrible happen and I lose my primary, I
00:14:15 - immediately know that that is a backup and I'm going to make
00:14:18 - it active. So it makes Rapid Spanning-Tree much faster than the
00:14:21 - original. Multiple Spanning-Tree
00:14:25 - is a way of grouping Spanning-Tree instances. You may know that
00:14:29 - Cisco does not actually run Spanning-Tree and Rapid Spanning-Tree.
00:14:33 - They run per
00:14:36 - PV Spanning-Tree and
00:14:40 - PV Rapid Spanning-Tree, which, you remember, stands for Per-VLAN.
00:14:43 - Well, that's great until you have 50 VLANs and your switch is
00:14:46 - just dying because it's got a Spanning-Tree instance on each
00:14:49 - one of those. Multiple Spanning-Tree allows you to group Spanning-Tree
00:14:52 - instances together to where, let's say I've got that was odd.
00:14:58 - Everything froze for a moment. I've got my typical Spanning-Tree
00:15:01 - instance right here. I've got 50 VLANs. Well, I can say one instance
00:15:07 - of Spanning-Tree is running for 25 VLANs and that's the root
00:15:10 - bridge for that. And then one instance of Spanning-Tree is running
00:15:14 - for the other 25 VLANs,
00:15:17 - and that's going to be the root bridge for that. So I run essentially
00:15:20 - two instances of Spanning-Tree for my 50 VLANs instead of 50
00:15:25 - instances all doing pretty much the same thing. So now let's
00:15:31 - blend all that into the key troubleshooting for Spanning-Tree.
00:15:36 - First off, let me just set the TSHOOT exam aside for a moment
00:15:39 - and talk about real world. If you have a Spanning-Tree loop in
00:15:44 - your network,
00:15:46 - people go, "What do you do?" You do what we all do. You run nil.
00:15:49 - You run. I mean Spanning-Tree is one of those bad-day scenarios
00:15:54 - where I mean the switch lights are blinking like mad. You can't
00:15:57 - access them via Telnet, sometimes SSH, because they're frozen.
00:16:01 - The processor is pegged. Switches are going down and rebooting
00:16:04 - computers. I mean the network is useless. Your servers are down.
00:16:07 - Computers are down. It's not good. You run into the server room
00:16:11 - and you just start unplugging cables, really focusing on your
00:16:14 - inner switch links first and then focusing on the PCs, if you
00:16:18 - believe that's where a loop is coming from. What I usually do
00:16:20 - is start unplugging one major switch at a time and find out where
00:16:25 - the madness stops to where I can at least tell what switch. I
00:16:28 - mean sometimes the chassis-based switches are huge with a lot
00:16:32 - of connections, but at least it will focus me on which switch
00:16:34 - then I focus on the module then I say, "OK. Here is the cable
00:16:37 - that's doing it. Let's trace this and find out who caused this
00:16:41 - whole thing." And unfortunately, it's usually something that
00:16:44 - you plugged in a couple of weeks ago and totally forgot about
00:16:46 - and someone did a no-shut somewhere at some point. That aside,
00:16:50 - they're not going to have, of course, a complete network outage
00:16:53 - on the TSHOOT exam because you have to be able to access the
00:16:56 - devices. So what you'll want to do is first off, check out "show
00:17:01 - spanning-tree. "Show spanning-tree" is your quick view of the
00:17:05 - Spanning-Tree network. It will show you what interface statuses
00:17:08 - are, what your current bridge ID is, what interfaces are blocked,
00:17:13 - what are forwarding, designated ports, backup ports, all those
00:17:16 - kind of things. It will tell you who the root bridge is in the
00:17:20 - network, the priority, just a ton of information, and it will
00:17:23 - show it for every single VLAN. This one is, I don't use this
00:17:28 - too often but it's good, "show spanning-tree interface detail."
00:17:31 - And this is, by the way, a variable to where you put in whatever
00:17:34 - interface you want to focus on. That will show you the actual
00:17:37 - cost of that interface. It will show you again the bridge ID,
00:17:43 - the root bridge ID, is this the interface that helps you reach
00:17:47 - the root, all the kind of how many BPDUs you're setting on that
00:17:50 - port, just a lot of kind of nitty-gritty troubleshooting that
00:17:54 - you can get. This
00:17:57 - one, I kind of threw this one in here, not directly related to
00:18:01 - Spanning-Tree, but if the switches are accessible and you suspect
00:18:04 - it's Spanning-Tree loop, do a "show process cpu." Spanning-Tree
00:18:08 - loops don't always take out the entire network, although they
00:18:11 - can, depending on the severity of the loop. So if you're looking
00:18:14 - at your CPU processes and you're at 90% and you're typically
00:18:18 - running around 5-10%,
00:18:21 - usually a Spanning-Tree issue at that point. I mean if you're
00:18:24 - just staying pegged, there is a loop in the network. And remember,
00:18:27 - when you have a loop, I mean when you've got a couple of switches
00:18:30 - I'll just draw up a quick scenario here and you get a loop in
00:18:34 - the network, you have immortal packets.
00:18:37 - Everybody thinks, "Oh, well, they'll die eventually because of
00:18:40 - the TTL." No. TTL is a Layer 3 field in the header. The only
00:18:45 - thing that decrements the TTL, the Time to Live, is a router.
00:18:49 - And if there are no routers in the picture, then you've got a
00:18:52 - packet that will live forever and ever, looping around and around
00:18:55 - and around, taking the network out. So again, when you do that
00:18:57 - "show process cpu", if it's just steady, pegged, a lot of times,
00:19:02 - you can go, "OK. Something is up and it's probably Spanning-Tree."
00:19:06 - So it's kind of like, "Well, what's that command for? Hmm." Yes.
00:19:09 - Go through and literally start shutting down again, I would start
00:19:15 - focusing on do a quick "show cdp neighbors," see what's ports
00:19:18 - are connected to what if you don't have a network diagram. Shut
00:19:21 - down the interfaces that are connecting neighbors and see if
00:19:24 - the processor suddenly drops because you may just strike gold
00:19:29 - and hit the port that is looping.
00:19:33 - Well, that should get our blood flowing on VLANs and Spanning-Tree,
00:19:36 - looking at the concept review to some of the key troubleshooting
00:19:39 - aspects for each one of these technologies. So let's now move
00:19:42 - in to the real troubleshooting scenarios. I hope this has been
00:19:46 - informative for you, and I'd like to thank you for viewing.

Switch TSHOOT: VLANs and Spanning Tree

Switch TSHOOT: VLANs and Spanning Tree, Part 2

Switch TSHOOT: L3 Switching and Redundancy Protocols Concept Review

Switch TSHOOT: L3 Switching and Redundancy Protocols

Switch TSHOOT: L3 Switching and Redundancy Protocols, Part 2

Route TSHOOT: L3 Connectivity and EIGRP Concept Review

Route TSHOOT: L3 Connectivity and EIGRP

Route TSHOOT: L3 Connectivity and EIGRP, Part 2

Route TSHOOT: L3 Connectivity and EIGRP, Part 3

Route TSHOOT: OSPF and Route Redistribution Concept Review

Route TSHOOT: OSPF and Route Redistribution

Route TSHOOT: OSPF and Route Redistribution, Part 2

Route TSHOOT: BGP Concept Review


Route TSHOOT: Router Performance Issues Concept Review

Route TSHOOT: Router Performance Issues

Security TSHOOT: Access List Concept Review

Security TSHOOT: Access List Chaos

IPv6 TSHOOT: IPv6 and IPv6 Routing Protocols

This forum is for community use – trainers will not participate in conversations. Share your thoughts on training content and engage with other members of the CBT Nuggets community. For customer service questions, please contact our support team. The views expressed in comments reflect those of the author and not of CBT Nuggets. We reserve the right to remove comments that do not adhere to our community standards.

comments powered by Disqus
Community Standards

We encourage you to share your wisdom, opinions, and questions with the CBT Nuggets community. To keep things civil, we have established the following policy.

We reserve the right not to post comments that:
contain obscene, indecent, or profane language; contain threats or defamatory statements; contain personal attacks; contain hate speech directed at race, color, sex, sexual orientation, national origin, ethnicity, age, religion, or disability; contributes to a hostile atmosphere; or promotes or endorses services or products. Non-commercial links, if relevant to the topic, are acceptable. Comments are not moderated, however, all comments will automatically be filtered for content that might violate our comment policies. If your comment is flagged by our filter, it will not be published.

We will be continually monitoring published comments and any content that violates our policies will be removed. Users who repeatedly violate our comments policy may be prohibited from commenting.

Course Features

Speed Control

Play videos at a faster or slower pace.


Pick up where you left off watching a video.


Jot down information to refer back to at a later time.

Closed Captions

Follow what the trainers are saying with ease.

MP3 Downloads

Listen to videos anytime, anywhere

Annual Course Features

Transcender Practice Exams

These practice tests help you review your knowledge and prepare you for exams.
Available only with the annual subscription.
Jeremy Cioara

Jeremy Cioara

CBT Nuggets Trainer

Cisco CCNA, CCDA, CCNA Security, CCNA Voice, CCNP, CCSP, CCVP, CCDP, CCIE R&S; Amazon Web Services CSA; Microsoft MCP, MCSE, Novell CNA, CNE; CompTIA A+, Network+, iNet+

Area Of Expertise:
Cisco network administration and development. Author or coauthor of numerous books, including: CCNA Voice 640-461 Official Cert Guide; CCNA Voice Official Exam Certification Guide (640-460 IIUC); CCENT Exam Prep (Exam 640-822); CCNA Exam Cram (Exam 640-802) 3rd Edition; and CCNA Voice 640-461 Official Cert Guide.

Add training to a playlist
or create a new list
Add to current playlist
or add to an existing list
Add to new playlist
Add New Bookmark

Switch TSHOOT: VLANs and Spanning Tree Concept Review
Bookmark Title:

Login is required to access this feature.

Your browser cannot access Virtual Labs
Video Options

This advanced buffering is applied to all streams regardless if you installed the doublespeed control or not. Sometimes the advanced buffering causes the video to hang or behave erratically. If you are experienceing issues with video playback please disable the doublespeed buffer.

Remember to re-enable the buffer if you want to use the doublespeed control.

If you are experiencing problems with our content delivery, please click here to switch to our alternate content delivery network or go to our network FAQ.
For other common video playback issues, including firewall and corporate network issues, please visit our Tech Support forum.