Try our training for free.

Gain instant access to our entire IT training library for 1 week. Train anytime on your desktop, tablet, or mobile devices.

This Cisco video training with Jeremy Cioara covers troubleshooting Cisco networks, including topics such as IOS tools, VLANs and spanning trees, router performance issues, and more....
This Cisco video training with Jeremy Cioara covers troubleshooting Cisco networks, including topics such as IOS tools, VLANs and spanning trees, router performance issues, and more.

Related area of expertise:
  • Cisco networking level 2

Are you ready to run a Cisco network?  You will be, once you pass your TSHOOT exam. TSHOOT is the final step for earning Cisco's CCNP certification.  Employers trust that CCNP certified staff have the vital, problem-solving skills their network needs.

With tech guru Jeremy Cioara in the virtual chair next to you, you'll get the training you need super-fast, and you'll love every minute of it!  His TSHOOT video course is 80-90% hands-on, and Jeremy's filled it with tons of unscripted, real-world troubleshooting demonstrations.

By the time you're done watching, you'll be ready for the TSHOOT exam and actively troubleshooting your own network.
1. TSHOOT: Setting Your Expectations (16 min)
2. General TSHOOT: The Troubleshooting State of Mind (28 min)
3. General TSHOOT: Troubleshooting Before You're Treading Water - Proactive Steps (18 min)
4. General TSHOOT: Troubleshooting Before You're Treading Water - Proactive Steps, Part 2 (39 min)
5. General TSHOOT: IOS Tools to Monitor and Maintain the Network (27 min)
6. General TSHOOT: IOS Tools to Monitor and Maintain the Network, Part 2 (56 min)
7. Switch TSHOOT: VLANs and Spanning Tree Concept Review (19 min)
8. Switch TSHOOT: VLANs and Spanning Tree (30 min)
9. Switch TSHOOT: VLANs and Spanning Tree, Part 2 (28 min)
10. Switch TSHOOT: L3 Switching and Redundancy Protocols Concept Review (21 min)
11. Switch TSHOOT: L3 Switching and Redundancy Protocols (36 min)
12. Switch TSHOOT: L3 Switching and Redundancy Protocols, Part 2 (27 min)
13. Route TSHOOT: L3 Connectivity and EIGRP Concept Review (23 min)
14. Route TSHOOT: L3 Connectivity and EIGRP (48 min)
15. Route TSHOOT: L3 Connectivity and EIGRP, Part 2 (37 min)
16. Route TSHOOT: L3 Connectivity and EIGRP, Part 3 (19 min)
17. Route TSHOOT: OSPF and Route Redistribution Concept Review (23 min)
18. Route TSHOOT: OSPF and Route Redistribution (41 min)
19. Route TSHOOT: OSPF and Route Redistribution, Part 2 (29 min)
20. Route TSHOOT: BGP Concept Review (18 min)
21. Route TSHOOT: BGP (26 min)
22. Route TSHOOT: Router Performance Issues Concept Review (28 min)
23. Route TSHOOT: Router Performance Issues (43 min)
24. Security TSHOOT: Access List Concept Review (17 min)
25. Security TSHOOT: Access List Chaos (62 min)
26. IPv6 TSHOOT: IPv6 and IPv6 Routing Protocols (21 min)

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

Switch TSHOOT: VLANs and Spanning Tree


OK. Let the adventure begin. We have arrived at our first troubleshooting lab. We're just going to be focused on VLANs and Spanning-Tree. The way this is going to work is I've got three different troubleshooting scenarios, and I'll explain how this all works as we get into it. But here is the scenario. We've got ASW1; one of the switches has failed. Scenario 2, we've got a guest access VLAN which is failing. And then scenario 3, the connection to ISP1 is down. Now at this point, I'm sure that's extremely vague, so let me explain further.


So now that we're at the troubleshooting lab, I can officially talk about how we're going to handle labs in this CBT Nuggets series. When I was first trying to determine how to do this series, I talked to the CBT Nuggets and I said, "This is really a hands-on series to where I mean if you take the certification exam for this, you get one or two simple questions to start the exam off I think just to get your blood flowing. And then you are in a


full-blown simulator for the rest of the exam. It's all hands-on. It's all real world. So I was talking with the powers that be at CBT Nuggets and I was, like, how do I do this? I can't really build my own troubleshooting labs because then I know exactly where all the flaws are and I'd record it and I'd be like, "Oh, OK, guys. Let's look at this. Oh, look at that interface. It


shut down. Wow. I didn't expect that." I can't pre-plan things thing that's I'm going to find wrong. I think at this point, if you've gone through some of my other series, you know I kind of go without a script and if stuff blows up along the way, I'm, like, "Hey, let's work through. Let's figure it all out together."


So if it were all scripted, I just would feel, I don't know, the series would be kind of wacky to me. So I was looking for a remote lab vendor, and I remember these guys I ran into at one of the Cisco networkers' conference called NIL. And there were some guys from, where were they? Slovakia? No. It's another


website. It's si. Silvonia? I don't even know. They're far away in another place in the world, far away from me. But all they do or one of their major focuses is remote labs. So I thought, well, let me check them out. And sure enough, they had a TSHOOT series. And so I talked to them. I said, "Hey guys, are you cool


if I use you guys, because you guys have some pretty sweet labs, and just kind of record it? And I'll suggest, of course, to our students that if you want, you can definitely sign up for the NIL Labs yourself and go through them, kind of get that hands-on experience yourself." But what I'd really like to do is just


go through the labs and record my thought process. Because one of the best ways to get troubleshooting skill is experience. You know that, right? We've talked about that up 'til now in the series. You know until you've been there and done that, and a lot of times, it's hard to do and I think about "How can I build a series that brings experience?" And I thought, and this word just keeps sticking to my head, apprenticeship. It's where


when somebody is becoming an apprentice, they just kind of sit under, I'm hesitant to use this word but it kind of goes together, the master, if you will. They sit under the master, like I think of like a swordsman, like the master swordsman, and they watch and they duel and they battle and they kind of learn from the master and just kind of gain that experience and then as Star Wars come back in, "The apprentice has become the master." So


that's what I thought I would do, not that I'm at all saying I am the master of all things Cisco because I'm not. Trust me, as I'm sure, as we go through the series, I'm going to run into some walls and go, "What on earth?" And I know many of you are going to be, like, "Come on. It's over there. It's over there.


Look under there." So anyway, my point is this: you guys can hang, you can watch exactly what I'm doing, but I also just wanted to throw the website out there. It's If you do want to go check out the labs, they do have labs. Of course, it is an extra cost to sign up for the labs, but they have subscriptions for a week, for a month, for three months, for however long you want to get into the labs. So that's going to be how I structure


it. So what we're going to do is kind of go piece by piece. I'm going to show the network diagram. I'm going to break down the scenario. And let me also mention this: when I went to the NIL labs, of course, the labs are in PDF format and they're huge. I mean they have full scenarios of, "Here's what's going wrong," and I thought, "Well, why don't I do this?" just because I don't want to sit and read paragraph after paragraph on the video to you guys. So what I did was I kind of summarized


the trouble tickets. These labs are a series of trouble tickets to where it will say, "Trouble Ticket A: User Bob, he came in in the morning and his coffee spilled. It was a bad day for him" This is kind of how the labs are at NIL. And I thought, you know


what? Instead of just having the full scenario, I'm going to boil it down. And so what I did was I recreated the trouble tickets on these slides and just used bullet points. I'm like, "Hey, Bob came in, switch didn't work." Or I shouldn't even say switch.


"Bob came in. Connection didn't work. He complained, sent a trouble ticket, says everything is down. What do you do?" So I just kind of boiled it down so you don't have to sit there and read and read and read all these paragraph formats. So that's my overview. That's going to be how we approach the


labs. Again, so I'm surprised when the trouble tickets come in, and I have to figure it out and then you guys can watch me, kind of watch my thought process, have your own thoughts, gain some skill, especially if you want to check out and do the labs yourself, put that all together. I think it's going to be a pretty cool


series. All right, well, let's get in to the lab topology. And this is going to be the topology that we use for the rest of the series. This is really neat because it's just like the TSHOOT exam. Cisco publishes, I don't know if you know this, but they publish the topology, the network diagrams that you're going to experience in the exam. So it would be very smart before you go take the test


to go to their website and look at them and kind of take some notes, all those kinds of things, get familiar with the lab topology because once you start the exam, you're going to get the same topology for the rest of the exam. And let me say thank you,


Cisco, for doing that because you know what it is, walking into a new network environment. It takes a while. You got to, "OK. This is connected to this. OK. This subnet is over here." It just takes time to get familiar with a brand new network. So just like the lab exam or the certification exam, we are going to be using a single topology throughout this entire series, and trust me, there is a lot that can go wrong with the topology like this. So let's break it down. Let me just hit the major


areas. Up here, we've got the ISP. So notice we've got dual ISPs going out right here, two different ISP connections. We've got a www, Worldwide Web, HTTP server that we can use for tests. Now this lab does not have actual Internet access, but we can always check this Web server to make sure that things are online and the Internet is working. This let me just draw a nice big circle around here.


It's big, very big. It's bigger than my drawing pad. So we've got this right here, which is, you could call it the corporate office. Think of this as HQ where all of our devices reach. We've got a server, represent a server farm over here on the right, and we do have remote desktop access to all the clients, all the servers connected into Core Switch 1. Now Core Switch 1 obviously runs the campus, connects to these two edge routers, that IRO1 and IRO2, which connects to our two different ISPS. We also have Core Switch 2, that's our redundant switch down here, bleeding into, it looks like, a client switch. So this is our client connectivity


and a client test over here, which is going to be our end users that are connecting through Access Switch 1. Corporate office also has dual connections to branch routers. We've got CRO1 and CRO2, which connect to some kind of cloud. At this point, I believe it's frame relay. So we've got a framer-like


cloud connecting to dual branch office routers. Now these are for the same branch office connecting into Branch Switch 1, which has Client 2 and Client 3. So this is our topology, and again, as we go through more of this, we're going to get more and more familiar with it. So we've got I guess you could say two major


offices branch office and corporate office and dual ISP connectivity. All right. Well, that should give you an overview of where we're going. Are you ready? Let's get into it. Scenario 1 in switch troubleshooting. Here are the high points. ASW1 has failed. Junior colleague was asked to replace it. Now just a side note, any


time in this TSHOOT lab experience or certification exam, any time you hear of a junior employee, something bad is about to happen. So enough said. So ASW1 is over here. It's in our corporate office. So it looks like that's a brand new switch based on the


scenario. Next morning, report came in, ASW1 does not work. OK. Simple enough. That's all there is to the report. We've got Client 1. I'm guessing that's our reportee in the system. So users on Floor 1 fed by ASW1 are complaining about network access and they need it repaired ASAP. Of course. Everybody is Quadrant


1, right? Urgent, high priority. So what I'm going to do is I'm bringing up the lab environment on NIL. And the beauty is I just kind of click the devices and get access. I've already clicked because I wanted to have the log on already to Client 1 over here so I have a remote desktop session here. Now keep in mind,


all of these are remote sessions from me until Silvonia where are you, NIL? I can't even pronounce your country name. It's horrible. It's a horrible statement for me. So there is a little delay. I mean I'm figuring isn't this amazing? As I click this button, the packets are traveling thousands of miles.


So anyway, let's get on to our client. And first I'm going to do is get into a command prompt, do a ipconfig. That's always my first thing, to check the IP address. It looks like we've got by the way, the clients, and I read this in the documentation from NIL, they all have two network cards: a lab network card and management. Now management is behind the scenes. It's for


the magic that NIL is doing, so don't even concern yourself with that IP address in these labs. We're looking at the lab. Imagine as if this client only had one network card and that was lab, and at that point, I would say that is bad because the client is not getting an IP address. A matter of fact, it's not even


a good old 169.254. They must turn off that feature on the client. So we're not getting an IP address so DHCP is not working. So let's do this. Let's go to where we have a failure point, ASW1. Let's start there. Just kind of follow the flow, right? So I've got my session


brought up here. Let's get in. So I'm going to do, and I'm telling you these are just my own habits and feel free to I should stop even talking. I'm just going to troubleshoot as if I was here, and if you have any questions, I'm sure I'll answer them. So I'm going to do


a "show ip int brief." That's always the first command I type almost any device I get on because there is no other command in Cisco that gives you not only all the interfaces but all the interfaces in a very concise format as well as their status, both Layer 1, physical layer, and layer 2, the data link layer. So I'm looking here. And by the way, this is all you get. We


don't have any diagrams with IP addresses, nothing with port numbers, nothing. We got to kind of discover this as we go. So I'm looking here. Let me get a little more because it looks like we've got some up interfaces. That's good. I'm going to do a "show interfaces status" because that's another, again, concise view of all the interfaces, and I get to see the descriptions. Now one thing that I can assure


you, and this really helps as you're troubleshooting, the descriptions are accurate. NIL is not cruel enough nor is Cisco to start putting bad descriptions like that this actually connects to the PC and they put a description on there saying, "Oh, that's really the channel." So the descriptions are accurate. I guess what I'm


looking for right now is what's up? My initial thought is I would see some down interfaces, which I see VLAN 128 is down. And I'm going to make an assumption there that VLAN 128 is the management VLAN. So let's do a quick "show VLAN." Let's take that one on


first. It's probably unrelated to what we're doing here. I don't see VLAN 128, so that's a quick add. I'm going to go in and do "VLAN 128." Let's create that VLAN, name, management. Now look at that. We've got some fancy logging going on too. So we've got name and management.


So that way, because if you have a VLAN interface, let me do, try "IP interface brief." If you have a VLAN interface and there is no associated VLAN that goes along with it, kind of you haven't created the Layer 2 VLAN, it's not going to come up. OK. So it looks like something happened here. We've got logging


reengage. It looks like some logging is turned on. And as soon as that management interface went active, it's saying OK. Good. We're reconnecting to our logging server. It looks like a syslog server that is configured. So that was good. It's a good first


step, get some management access back to this. And by the way, when you click on these devices on NIL, you get a console connection. So you can access them regardless of whether the device is up. So next piece I'm going to do is get my interfaces back in front of me again. I'm going


to do a "show cdp neighbors." Again, I'm assuming CDP is running, and I'm not seeing anything here, so I'm stuck. I'm, like, "Wow, this went well." OK. So we're up. OK. Let's see what we know, right? We're up. We've got our interfaces showing connectivity.


I'm not seeing any CDP neighbors, so let me do a "show run include CDP," make sure CDP is not turned off. OK. It looks like it's not enabled somewhere under some interface. Well, again, by the way, "no cdp run" turns it off on the whole switch. "No cdp enabled" just turns it off on an individual interface.


Yes, there it is. OK. So that makes sense. So we've got a link to the client which is not having CDP enabled, so we should see, I'm guessing, if the other side is turned on, we should be seeing things via CDP. So OK. Here is my next step. If I'm at this point


in the real world which this is very close to the real world; Jeremy is already confused I'm looking. I'm seeing the interface is up. I'm thinking it's connectivity. I'm going to start seeing what's going on. Let's do a "show interface status" and see what's oh, not "show ip interface status," "show interface status," and let's see what's connected to what and see some configurations. So I'm looking here. It looks like I've got some


individual interface configs on Fa0/1, 0/2. And we've got Port Channel 1. So let me do a "show run interface port channel 1," po1. All right. So here is what I'm going to do. I'm going to grab one of my favorite utilities, Notepad++. Nice free utility. I'm just going to copy this so


I can use it as reference as I'm jumping between the switches. Now if typically, if you don't have Notepad++ available, for instance, if you're on a certification exam, you just keep two windows open, kind of organize them side by side. The exam lets you do that. I'm just going to keep that there so I can flip


back to it quickly. So let's focus first on the connection between ASW1 and CSW1. I'm going to come over here. I want to make sure CDP is enabled on CSW1 as well because obviously, I'm not going to see anything. So let's do CSW1, show IP interface brief.


All right. A few more interfaces here. Wow, a lot more VLANs. So this is obviously a core switch doing a lot of routing. It looks like the interfaces are up for the most part. It looks like a 48-port switch with most of them unused. Again, and trust me, if the trouble tickets all take this long, we're in for a long ride on this series. But what I'm saying is right now, I'm


getting familiar. You're getting familiar with this topology. We'll get used to where things are connected the more that we do. So let's do a "show interface status" so I can see what's connected to what. All right. So Fa0/11 and 0/12, it looks like our trunk to ASW1 looks good. OK. So we're good there. Let


me space down through this. OK. We got Channel to CSW2. So if these physical interfaces are channeled, that means there is going to be a port channel. So let's draw up then. There we go. Port Channel 1, let's do that, "show run interface po1." All right. So port channel 1, I'm just going to take this, paste it next to this guy. Let's kind of look at the two. OK.


We've got the same allowed VLAN, same native VLAN. We've got trunking enabled. Oh, oh, whoa. That's not been used for a while, switchport trunk encapsulation isl. Nice. I don't even I don't even think the 2960, which is what our little ASW1 is, supports ISL encapsulation. That is pretty tricky. OK. That


gives me a quick view of what's going on there. I'm going to do a "show run include CDP" to see if OK. It looks like it's turned off in a few places there. I don't see it turned off on the port channel and I don't see a "no cdp run" so it's running on this switch. So if it's not turned off on the port channel


and it's running, then it should show up. So let's fix that error that we saw there. I'm going to go under interface port channel 1 and do a "switchboard trunk encapsulation dot1q." Let's get that switched over to a modern trunking language. OK. So we've got that executed. Did that fix anything? Let me


shoot over to Access Switch 1. Oh, look at that. Life. Spanning-Tree PVSTSIM_FAIL blocking designated port. OK. Inconsistent VLAN. OK. Well, that's OK. That's OK. That's a problem but that's OK because now we have OK. We have some connectivity. The interface has been enabled. So I'm seeing


CDP packets on there. So now it looks like there is another issue going on here, which is Spanning-Tree. But for now, you know what? Before I go any further, I'm going to check connectivity to CSW2, just make a little note for myself here. ASW1 Spanning-Tree issues to CSW1. So I don't forget about that. OK. So we've got ASW1 with connectivity now to CSW1. And before I go any further, that was pretty scandalous. What they did was they mismatched the trunk encapsulations. CSW1 was using ISL, ASW1 using 802.1q. The reason, I'm guessing, they went with that little flaw in there was because the interface stays up. You still have connectivity. You still are up and up.


You're not going to see the line protocol go down. So it looks like everything is working but you're not communicating because you're speaking different languages. So let's shoot over to CSW2 because we're not getting connectivity to that guy either. All right. Default neighbor not on common subnet. OK. So we got


something going on there. So let's do a "show cdp neighbors" on this guy. I just want to see what I'm seeing. All right. So it's C Switch 1. Who are you, not default neighbor? "Show ip interface brief." Let's see if we can find port I'm guessing if they stayed the same that this guy is going to have a port channel 1. Oh, notice that. He is completely down. So this is a totally different issue. It looks like as if it


was a trunk mismatched, then we'd have up and up. So let's do "show interface port channel 1." Look at the config under there. OK. So it looks like they've got dot1q turned on, switchboard mode trunk. OK. So it looks like port channel 1 is good, and we just keep getting these errors. OK. So port channel 1 configs look good, indiscernible. Let's do a "show


interface status." Let's see what physical interfaces make up port channel 1. OK. So whoa. Look at that action. Suspended. No sup for you. So FastEthernet 0/11 and 0/12, "show run interface fa0/11 and /12." OK. OK. Now wait a sec. OK. Look at this. Port channel 1, they've got switchboard trunk allowed thank you, status message switchboard trunk allowed VLAN such and such, but on the physical interface, they don't have that.


So here is the tip. If you do the "show interface status, you see suspended I got to turn off that auto scroll on SecureCRT. You see suspended right there. That typically is because a physical interface is not matching the configuration of the port channel.


Good grief! They threw the whole kitchen sink at us on this first trouble ticket here. So let's go in. Let's go under fa0/11. And what I'm going to do is I'm going to make the configuration of fa0/11. I'm going to turn off the auto scroll. That's what I'm going


to do on SecureCRT. I'm going to copy and paste this before it scrolls down on me again. There we go. OK. So I'm going to put switchboard trunk allowed VLAN on there. Look at that. Hey. Hey. Hey. You can't make this much noise when you're in the certification exam as you solve things, so we might as well while we're out here.


Look at this, fa0/12 still complaining, set it up a couple of times. Wham. We should see that bad boy come up. Look at that, changed up. Hmm? Hmm? Show cdp neighbors. CDP is such a handy thing. Yes, I don't see anything. But CDP has a 60-second timer so let's give them some time. Show interface status. Good. What we see is we've got FastEthernet 0/11. We're connected. We're good. FastEthernet 0/12. All right. All right. I've got to get my bearings. I'm sorry, guys. I'm jumping all


over the place. OK. So where are we right now? We've got now connectivity going to ASW1. Let's shoot back over to ASW1 because I'm starting to get lost as to where I am. I'm solving problems but I'm, like, "Where? What problems am I solving?" OK. It looks


like we're still getting this Spanning-Tree issue. We'll get to that next. Let's do a show CDP neighbors from ASW1's perspective. Sweet. OK. So ASW1, at least now, at the data link layer, we'll say, has connectivity to CSW1 and CSW2. Good. Good, good, good. So let me just put my thoughts together. OK. Let's figure out


this Spanning-Tree deal, all right? So we've got blocking designated port channel 2 superior BPDU claiming root such and such. All right. So let's do a show Spanning-Tree and see what's going on there. All right. So we've got, whoa, we've got, it looks like both of our port channels are blocked.


Spanning-tree is blocking both of those guys because it looks like with this arrow. Let's do a show Spanning-Tree inconsistent ports. PVSTSIM inconsistent. PVST. PVST? We've got MSTP up here. That's not working. So what we're doing, it looks like somebody configured ASW1 for Multiple Spanning-Tree Protocol. Let's shoot over to CSW1 just because it's right here. Let me do a show Spanning-Tree.


Yes. Yes. Yes, that's not Multiple Spanning-Tree. That's Rapid Spanning-Tree, my friend. We've got a mismatch in Spanning-Tree. That's your standard mismatch. Let's check out CSW1. I'm sure right some of you guys are, like, "Oh my word, is this whole series going to be like this?" I'm sorry. Once I'm in troubleshooting mode, I'm there.


I'm there. I'm just, I'm kind of like, "OK, let's figure it out." Maybe this wasn't a great idea. Maybe it was. As long as you guys are following along, we'll see. We'll see how it all turns out. So we've got Rapid Spanning-Tree Protocol running on it. OK. So that's our issue right now, is we've got a wrong Spanning-Tree


version running on ASW1. So let's do a show run include spanning-tree. Yep, right there. Spanning-Tree mode. It's not RST or MST. It's Rapid, Rapid PVST. Let's see if we get some happy messages. Look at that. Line protocol changed up. Logging started, reconnecting.


Yes, my tone will go up every message I get. I guess it's not going to tell us we're happy. Let's just do a show Spanning-Tree. It always tells you when something is wrong, never when something is good. Good. OK. Now I know some of you might be looking, being,


like, "Ok. Blocked. Well, that's not good." Well, this is good. Look at our topology. This is a redundant connection so obviously, one of these ports is going to have to get blocked because Spanning-Tree stops loops. So it looks like Spanning-Tree decided to block


port channel 1, which is fine. It doesn't matter which one gets blocked, at least in this case, because this guy right here, port channel 2, is now active. So we've got root connectivity going through. Wow. I think we've solved a lot. Let's go back to the client.


Let's do an ipconfig. Let's see if we get an IP address. I'm guessing DHCP should be running, right? Let's see. Hey. Look at that. TShoot? That's TSHOOT. I'm an idiot. TSHOOT.local is our domain. OK. So we've got an IP address. Let's see if we can ping the


default gateway, Ah, such a good feeling. Good. Good, good, good. So at this point, what I would say is save those configs. I would say at this point, connectivity issues are resolved. Now, granted, in the actual lab, they would have testing steps saying, "Do this, do that." But I would say I should add


that. I should make sure I add that to the future scenarios, is how to know when something is fixed. Because at this point, I would say we have connectivity. We've got network access. Once those leases are renewed, we're good to go. ASW1 looks good. All of our ports are up and forwarding. I would say we have a


successful solution. Now I'm sort of creating the plan for this as I go. I hope you don't mind. But what I'm planning on doing is once we reach the end of the entire group of scenarios, I want to look at the solution guide from NIL and kind of have a debrief to where we go through and say, "OK. Well, this is what we found. This is what NIL said


we should have found," and kind of work through it there. So I will do that. That's what I'm planning on doing. But since we have only done scenario 1 at this point, let me just kind of debrief on what we found there. Some of the key facts that we noticed is 1) there was the trunking mismatch. So I'll just put mismatch isl/dot1q. And that's what allowed the interfaces to show up except there was no communication going across them. CDP wouldn't even show neighbors on that. So we


resolve that and that brought up the connectivity to Course 1, I believe is what it was, and then we found the Spanning-Tree issues. STP was misconfigured and we had MSTP and RSTP mismatched to where the access switch was configured for Multiple Spanning-Tree and the course which is where it configured for Rapid Spanning-Tree. And that brought up connectivity for scenario


1, to where now, ASW1 is connected. It's able to communicate. The clients attached to ASW1 are connecting, able to communicate. So in the next Nugget, I'm going to pick up there and we're going to move into the guest access failure scenario. And once we reach

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

Please help us improve by sharing your feedback on training courses and videos. 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
Intermediate 13 hrs 26 videos


Basic Plan Features

Speed Control
Included in this course
Play videos at a faster or slower pace.

Included in this course
Pick up where you left off watching a video.

Included in this course
Jot down information to refer back to at a later time.

Closed Captions
Included in this course
Follow what the trainers are saying with ease.

Files/materials that supplement the video training

Premium Plan Features

Practice Exams
These practice tests help you review your knowledge and prepare you for exams.

Virtual Lab
Use a virtual environment to reinforce what you are learning and get hands-on experience.

Offline Training
Included in this course
Our mobile apps offer the ability to download videos and train anytime, anywhere offline.

Accountability Coaching
Included in this course
Develop and maintain a study plan with assistance from coaches.
Jeremy Cioara
Nugget trainer since 2003