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


Welcome to the CBT Nuggets Cisco TSHOOT Series. My name is Jeremy Cioara and I'll be hanging with you as we you go through this series and put the capstone on the Cisco CCNP track of material. Now for those of you that have had CBT Nuggets Series with me in the past, you know that typically the first Nugget of the series I spend just kind of talking about Cisco certification, how you can get the most from the series, you know, best practices, those kind of things. I'm going to change it up a little for


Cisco TSHOOT because I am figuring by the time you've got in here, you've gone through some other CBT Nuggets material before or you already know what the Cisco Certification track is all about because Cisco TSHOOT should be last. The other couple of exams that you can take for CCNP, you can take them in whatever order you want. Take Route first, Switch first, doesn't matter.


But TSHOOT has to be last because it takes all the information, the culmination of both Route and Switch, puts in to do a big blender and grinds it all up in spits it out in troubleshooting format. So what I'd like to do in this nugget is, do a fly by review of the CCNP. It's a great track, I want to just give you


again the overview of it. Then I want to take you into the troubleshooting state of mind. And that was really my toughest thing when I was putting this series together, I thought, "How do you build a training series that teaches people how troubleshoot because troubleshooting is so much experience and it really rides on the experience of the person who is doing the troubleshooting." And


while I still maintain that is absolutely true, there are some best practices and some mindsets, that's the best way I can put it. So mindsets that you can get into, that you can more effectively troubleshoot and more effectively approach situations that you encounter everyday. And that's where Bob and Carl are kind of


come into place. And then finally I'll wrap-up by talking about successful network maintenance. So here it is, the Cisco Certification Track, in my opinion one of the most rewarding certification programs that exists in the world. And I'm coming from a perspective of I've gone through


the Novel Certification Program, I've gone through all the Microsoft Certification Program and they're great. I'm not downing them in anyway, shape or form. But Cisco is a land that if you love it, if you like Cisco and the technology, you can land here in their certification program and never leave. Meaning there is


never a way that you can learn everything about everything in the Cisco world. So we're talking about CCNP here which is, this is a glade 2:35:0 where most people go first and I would say, more recently, Ciscos ha changed it to probably skew those statistics even further. CCNA is he beginning of everything. No matter what


direction you want to go, the CCNP track was revised to be three exams. And I mentioned them already, Route, Switch and TSHOOT. I've taken all of them and they are phenomenal exams. I will say, I guess before I say anything else, let me first finish my discussion. The reason I say Cisco wants to skew it further


is because this is only three tasks. Whereas, if you go in the direction of voice or security, you not only have to get your CCNA certification in that specialty, in addition to your existing CCNA, but you also have to pass four or five exams for the CCNP voice or the CCNP security as well, which just means it's a gob of exams to get there. So, going to CCNP not only is it just


more logical to go that route initially for most people, but it's just easier. There is just a lot less exams that you have to take to go that route and it enhances all of the knowledge that you have when you have when you go into these tracks. People ask me well, "Shoot, you know, I really want to go into security.


Should I get my NP first?" And I will always say, "Oh yeah, definitely. Get your NP first because that will only enhance you're going to learn in security. A lot of the concepts will open up easier for you if you go that direction." Now, what was I going to say?


Oh the exams themselves. The exams themselves are becoming more and more awesome every time I go through them. And I've seen, I will say, I got my CCNA certification, this was back in, I want to say 1999, maybe 2000, just right around there. And got my CCNA certification back when it was purely multiple choice and I will, and this is back when the CCNP exam track was four exams, I actually got my CCNA and my entire CCNP in one and a half months. Could you not from knowing nothing about Cisco all


the way to becoming a Cisco Certified Network Professional in one and a half months. Now, you might say, well, "Did you really know it?" "Nope. But I'm good at multiple choice exams," I can say that. So I was able to pass exams without really knowing the information and what's kind of funny is, was about three months later, I took my CCIE Routing and Switching and I just got nailed. "Welcome to the real world," as Morpheus would say,


right. This totally smoked me and I realized that this, back then, did not prepare you for anything CCIE. Ten years have gone by and a lot of revisions have taken place and I can tell you what, these exams are fantastic. I will say the Route and TSHOOT exams are definitely at the top of my list of like, wow, those are really cool exams. The Switch exam, it's


kinda cool. But I think it still needs work to become like Route and TSHOOT simply because there is a lot of questions on there that are kind of like, "Okay, put the list of design steps in order. What comes next and that, ah." It's not very real world on some of the questions. But, I will say it's definitely getting


there. Route and TSHOOT on the other hand are just phenomenal exams. TSHOOT, the one we're talking about right now, almost entirely hands on, not configuration wise but diagnostic. Did I just make up a word diagnostic-wise, we'll go with that. The two are, you actually are dumped into a simulation after simulation after simulation where they're saying, "Hey, these users got this issue, what do you think?" And you have to go and diagnose the problem. You can't fix it, because you're troubleshooting,


right? You just want to see what the problem is, correctly identify it and then answer the questions based on that. So, very good exams, very much in line to prepare you for a CCIE Certification. So as I promised, I'm going to cut myself short on the CCNP description, if you want more on that, check out Route, Switch, I dive a lot deeper into CCNP, why it's awesome, why you want to get it? I'm assuming, by time you are here, you know it's awesome, you know you want to get it, so let's talk TSHOOT. I want to start off


by looking at a day in life of two guys. The first one being Bob. Who is Bob? Bob is a CCNP level technician. He's passed his certs, he's working fulltime at a company called Medistart Financial. Now Bob, he's a nice guy. And when he get, you get to know me, he takes care of issues when they come up, he is friendly, he is personable, people like to call him. He goes


above and beyond, like when somebody calls his cell phone, he will absolutely answer it, if he doesn't answer it, people think, "Wow, his wife must be dying or something," because he always answers his cell phone. And you send him emails anytime, day or night, I mean, it could be one in the morning, send him an email, his cell phone is set to go "bing" anytime he gets an email. So he is up at one in the morning, he is checking it because


I "binged" him out of his sleep, he says, "Oh, I can care of that," because Bob is awesome. He jumps to fix any issue out there, ask anyone, ask anyone who knows Bob and they'll be like, "I love Bob. Bob is the man, he is awesome, he gets stuff done." So,


how is Bob's network? It's good on most days. I mean for the most part it's good, it stays up most of the time. It doesn't run as fast as he'd like. He's going to fix that. He's going to get to that at some point. He's going to create a project plan for it and maybe do it during the next upgrade cycle or something to really figure out why things aren't running quite and sometimes just weird things happens. And Bob, you know, again,


Bob being awesome, he is CCNP, figures it out, fixes it and moves on to the next thing, next call he's getting and so, that's the life of Bob. What he spend most of his life doing? Oh, answering emails, phone calls. He, you know if, there's a break in that,


he is checking out what's new. He is going to my blog and finding out what the new SNMP utilities are that a router that are cool and free and something you can tinker with on Linux and just play with. You know, he is just an--he is a techie guy by nature,


that's what he likes to do. Is he happy? Yeah, I'd say for the most part, yeah. But kind of overworked. The guy works on average, probably about 60 hours a week and he's just tired. He hasn't taken a vacation in years. I mean a real vacation where he can


leave everything behind. You know, he's on the beach with his wife and the cell phone "bings", he's like, "Oh, oh, I just, I got to take care of that, hang on, one second." He runs back into the condo, connects the VPN, he takes care of it because Bob's the man. But he's just--he's just tired. And things just


don't run the way he liked. So let's contrast Bob with Carl. I know what you are thinking. You are looking at picture, "Okay, Carl is what? Independently wealthy, sitting at yacht somewhere." No, Carl does work. He is a fulltime CCNP level technician working at Plentyserve Peanuts.


He is just doing something Bob barely has a chance to do. And that's take a vacation. Get away from it all and leave it behind. His cell phone isn't even with him. He left if back in the States and he is sitting on a beach somewhere with his wife, not pictured here. Just reading a paper, doing


what you do on a vacation. So, the question is, what makes Carl different? Well first off, he is an equally nice guy. So there is nothing about his personality that's different than Bob that makes people go, "Oh well, I like Carl more. Let's give him a vacation." People love chatting with Carl but the things is,


not many people have Carl's cell phone number. He doesn't give it out. He says, "You know what, the best way to get me is to email me or actually email the support email address that goes to a team of technicians. And they can filter it down through commonly asked questions and things like that." So, he goes with


email, he's not really immediately available because he takes a project based approach to life. Not just work, life in general. He says, "You know what, I'm going to schedule my life in such a way that I see things in terms of projects, not fires that come in every other day and I have this list of issues that I work through." Sure there's some interruptions, occasionally,


he gets a call, he's like, "Hey, something is down." But, chances are, he knows about the issue before he gets interrupted. Before the call actually comes in, because he's got a network monitoring system that has told him about it and he's already either fixed it already or he's got somebody on the way to take care of the issue. Reason why is his network's designed in such a way that


it's redundant. It has fail over capability. It's been tested and it's thoroughly put together as a complete system. Now, again, I know you are hearing me talking like, "Okay, yey, Carl." It's kind of like, "How do I get here?" Well that's the point. Is


that I, I will say I am, I am 80% Bob, 20, no, 10% Carl and 10% of ambition to be like Carl. Like I am the guy that I love putting out fires. I love being the superhero coming in, let me solve your issue. "Oh, yey, good job. Okay, we took care of it. Man,


that guy was awesome. Did you see him?" There is something to be said about being good at fixing things but there is something to be said about building a network that doesn't have to be fixed. That's what TSHOOT is all about. Now you might be thinking, that's not what TSHOOT is all about. TSHOOT


is about troubleshooting, isn't it? Not Bob and Carl and how you manage and maintain your life and your network and now, I'm looking at Stephen Covey. What's going on here? Well, if you look at the exam objectives for TSHOOT, you're right. TSHOOT is all about troubleshooting. Look at this, I'm going to scroll


over here to the exam description document on Cisco's website. TSHOOT exam topics, Blueprint. And if you looked on your troubleshoot, troubleshoot, troubleshoot, troubleshoot, just troubleshoot after troubleshoot. But look at this, there is this divide. There is


this section up here, it's smaller, albeit it's smaller, yes. But there is a section dedicated to maintaining and monitoring your network performance, like, developing a plan to monitor and manage you network. How do you perform that work monitoring using IOS tools? What are routine maintenance? What are, how do you isolate sub-optimal network operation and things like that with the OSI model. And, this is what I'm talking about


right here. Cisco thought it was so important and they said, "You know what, we can't just make a troubleshooting course about just troubleshooting even though there's a lot of it in here." They want to make a troubleshooting course that first off, tells you, "This is the best way that you should manage your life in the Cisco realm. Then if you do that right, you shouldn't have


to live in this layer too long because your troubleshooting is minimal and when it does happen, you've got such a well planned out network that the troubleshooting goes much faster than if you would just be putting out fires like most people do with that." So, now this, trust me, there will not be Stephen Covey


on the exam but when I was looking at some of the Cisco material for TSHOOT, I thought, "You know what, this just has Stephen Covey written all over it." I, just as a side little comment, I am the most blessed man alive because before I even knew about Stephen Covey, I lived all of my life and still live most of my life in this, they call it quadrant one where everything is urgent and important, no matter what it is. I get a phone call,


they want me to do something, it's urgent, it's important, I got to do it now. I hang up the phone, oop, an email just came in, it's urgent, it's important, I got to do it now. It's got a little exclamation point next to the subject and I got to do it, got to do it. And I ended up getting married to my wife who


actually became a certified trainer for Stephen Covey's Seven Habits of Highly Effective People. And it's funny because she began teaching all this kind of stuff and she came out and still to this day on my wall, if I look behind me, I still have four quadrants because she is still trying to organize me and I want to be organized. It's just not my nature to be there. And so


the goal is that, you design a network that you live in quadrant one and quadrant two. Meaning, primarily, your focus is in quadrant two where you are working on things, you are planning, you are setting up prevention, you've got value clarification, you're exercising things like that. You are living


in this land of "not urgent, but important." Meaning you're focusing your time on doing things that are not going to explode if you don't do them, but they're important. And if you don't do them, then you're eventually going to have these things move over to quadrant one for instance. Think of this as it relates to network


planning. If you don't do a preventative measures, you don't have IOS backups, you don't do backups over your configurations, you don't have redundant equipment, you haven't taken the time while it's not urgent to design things right and then something fails, you're now living in this quadrant one where you're trying to restore routers, networks down, pressure stress and you're--you can't survive there. I mean you can, but it's going to--you're


going to be living Bob's life. Working 60 hours a week. You get by but you're just tired of doing things. Whereas, by setting things up and planning the network out appropriately, you're good. And you can use this for anything in life. I mean look at this, exercise, exercise, I will absolutely tell you, is most of the time not urgent but it's important. It's important to


run to get some exercise, to stay healthy because otherwise, you're in quadrant one with you, I don't know, liver failing and bladder control and I don't know, what else medical you think go wrong. But you get the point. Your goal is to plan out the network in the non-urgent but important state. Now,


it's goofy because many of the IT people's mindsets are not this way. Most of us, and I will throw myself under this bus, live in this quadrant four where we just have, junk mail, trivia, busy work, phone, emails, time wasters, just escape activities. Matter of fact, when I was making this slide, let me just tell you just how bad I am. I put this thing up here, I was searching


Google to give me a chart of Stephen Covey's Seven Habits quadrants and I pasted in there and I was like, "I wonder what, I wonder if he has come out with anything new?" And before long, I signed, I went to Stephen Covey's website, I signed up for the Covey Community. He actually has a community to where you have accountability


partners, and that like, this side right here took me probably 60 minutes to create even though it was a simple paste from a phrases and thing because I'm now signed up for everything Stephen Covey. So, I'm living right now in the quadrant of waste and non-important stuff where I should be planning preventing and I should just go for a run right now. So while Stephen Covey may not be on the exam, the mindset


that he tries to communicate a lot is on the exam which is troubleshooting and network maintenance go hand in hand. If you have a good network maintenance strategy, then you'll typically have troubleshooting. For example, these are all maintenance things that happen right here on the screen. Which of those could lead to troubleshooting:


installing a new device; upgrading an IOS version; monitoring your network performance; security audits; implementing user requested upgrades; documentation. Now all of these would go under maintenance and all of them, I know, that some of you are halfway through, like yup, all of these, all of them could lead to troubleshooting, simply because, as you're adding a new device, it could cause something to go wrong or not fail over correctly or do something unexpected that now leads to troubleshooting.


You might be documenting the network, discovering areas and putting them down on paper and all of a sudden you look, "Oh, I didn't know that was there. Wow, is that working?" I didn't, I didn't, it's again, each one of these things could uncover something or cause something to happen in the network that causes you to go into troubleshooting mode. Now,


you would typically hear people say, and they usually say, with a southern drawl while they're chewing on a piece of grass or something, they'll say, "Well, if it ain't broke, don't fix it." And I know, some of you are smiling because you've said that before and I've said it, too, if it's not broke, don't fix it. It's true, there is some truth to that, yes, if it's not


broke, don't fix it, don't add a new device, don't upgrade the IOS version if you don't need to. There's good practices behind all these things. But at the same time, there's a lot of times where, if it's not broke, you still need to do maintenance so that you don't have to fix it later. For example, you may need


to upgrade the IOS regularly to prevent security flaws. It's like turning off Windows updates on a Microsoft server, why would you do that? Because it's going to, have security flaws if you don't act at a quickly protect it and all of that. So that's why Cisco really does want to communicate maintenance and planning and regular routine things that you do go hand in hand with troubleshooting. Just


give you an example. I got a call couple of weeks ago on the Microsoft side of things. Someone said, "Hey, I'm having some issues accessing this file." So I logged on to a Windows server and just, did some basic looking around at some troubleshooting, and all of sudden I looked at the event viewer and it was just full of these red error messages. And I go, Ah,


crap." And then and I start scrolling down the error messages, I'm like, "How long has this been going?" And I scroll and like, "This has been going on for three months. There has been this error and nobody is reporting, nobody's, my word, how did I miss this?" And then I go to the "I need to check the server more often. I need to, the I need, I need, dadadada," all of these


things that he need to do and all of a sudden email comes in, I looked this little preview Window next the to clock, I'm like, "Ooh, a message, I need to open it." And before long, all of the "I needs" are lost in this whirlwind of, "I've got to put out the next fire." So all these things go hand in hand to having


a solid maintenance plan and good troubleshooting skills, really do relate. Guys, I've got to tell you, God himself is testing me right now, because as I was recording the last slide, I glanced over because my cell phone was ringing and I looked at the caller ID, I was like, "Oh, that's one of my clients. I should check that." But


then I was like, "I can't do that. I can't check that voicemail. I just got done talking about the fact that we shouldn't be putting out fires every two seconds." So right, I am gritting my teeth to talk about keys to successful maintenance while not checking that voicemail in my cell phone even though it's going, "beep beep" every two seconds to remind me that I have a voicemail right there. I'm not going to check it. So,


let's wrap up with this. This is actually the last slide. I'm going to expand a lot more on this as we go through out the series. But there are some keys to successful network maintenance. First of, have a plan. Now, there are many models out there and I will


say, you can get lost in models. There is FCAPS, there is ITIL, there is Cisco PPDIOO and Cisco, of course, likes to propose that one because they created it, it's the Land Design Implement Operate and then Optimize. It's kind of this big circle you keep going on. And what these


are, I mean, if, I'm sure many of you have heard of ITIL Certificate which is the IT Infrastructure Library. You could get lost in it. I mean, seriously they have, I'm not going to say anything mean about ITIL, I was going to, but I'm not. They a lifetime,


you can spend it just learning how to plan and properly optimize things. And there's people who do that. So, I'm not saying go out and spend the next year in ITIL until you've got your own design. What I am saying, though, is have a plan, create your own plan if you want to. Model 1, Cisco's is a lot simpler than some of these other ones. To create model of how you should be


doing network maintenance. What are the best processes that you should do monthly, weekly, quarterly, annually to make sure that your network is optimized to the best possible configuration. Then, once you create that plan, schedule the tasks within your plan. For instance, how to schedule for when you have moves,


adds and changes? So, the old PBX people would call those max, where they would move different phones around in the infrastructure. And we have the same thing in the IT world. When do you add new devices? When do you move switches or routers to different areas? How do you replace failed devices? What's the process for doing this? Do you have backup devices? Are they redundant? What kind of process do you have for that? What's the process for software upgrades? Do you only upgrade when you need a feature from that? Hopefully not, hopefully you have quarterly or annual or bi-annual sort of method that you say, "Okay, all the devices are going to be on the same IOS version." I can't tell you how many times


I've been frustrated when I log on to a device, go to implement, like a quality of service feature and it's not there and I go, "Ah, good grief, when was the last time I upgraded this thing?" And I look. It's on IOS 12.2 or.1 or something I'm going, "Good grief. I need to upgrade this thing and get it on the regular


routine upgrade." How often do you update your documentation? Is it just once everything is falling apart. And you go, "Man, we need a plan," and you spend a week of creating this beautiful printed notebook of all these documentation and then, and you say, "Okay, there it is. Good job." You put it on the shelf and


don't refer to it till the next year is around and you go, "Oh no, I need to update that again." You throw the notebook away and start all over again. Did you see what I'm saying? Do you see what I'm trying to propose as we're doing this is just, having a plan that you're always, always in a proactive method of maintaining the network rather than sitting back and being a reactive state. The


last part of having successful network maintenance is to create a Sign Maintenance Windows. And for some organizations, this is easier than others, but policy, think about this. Email goes out to the organization, says, "From 1 a.m. till 4 a.m. on Friday or Saturday, something like that, the network will be unavailable from henceforth."


Now I know some of you are going, "Henceforth, what do you mean? Like all the time? Are we always going to be awake now on Saturday from one to four?" No, I'm not saying that you're down Saturday from 1 to 4 a.m. But what you've done is you've said a precedence. You've said, "You know what, from hereon out, the network maybe down from one to four." Now, you never said it will be and I


would probably suppose that 99% of the time it will be up during those hours. However, it's been set that there's a precedence that if somebody wakes up at one in the morning, so I go, "I got to check email," and email server is not online, you go, "Oh yeah, that's right. I forgot it's 1 a.m. on Friday, we have a network maintenance. Okay, I'm cool with that or something


like that." Have assigned network maintenance windows and that gives you the freedom to always have an area to do your upgrades rather than every time, you're now sending out an email interrupting business, to say, "Oh hey, we've got to do this." People, people


get used to it. For instance, I ordered a lot of equipment from a distributor every Saturday from, what is it, like 8 p.m. till Sunday on 1 p.m., their side is down. It comes up with a big, "We are down for upgrades and maintenance and these kinds of stuff." Initially I was like, "Oh man, that's a bummer." But


then now, I'm like, "Oh yeah, I just can't order on Saturday." That makes sense to me, that's okay, you adjust to it. And rather than, yeah, you get the point. So this gives you a window to always do all the things that you are hoping to maintain. So your goal when it comes to troubleshooting is to be that guy. That guy


right there. I remember seeing the Simpsons episode a long time ago and it's--for some reason I remember was, somebody sending an email to somebody else and for a brief moment, like 5 seconds, they flipped to the scene and the show the email like, "Fly through Cisco routers." I go, "Oh, that's awesome." So that is a real


scene from the Simpsons. It--I don't know his name but your goal is to be that guy. Who's sleeping comfortably not on the job but, he feels comfortable that his system is working and it's maintained and it's operational all the time. That establishes the framework for this troubleshooting state of mind.


You want to walk into a system that you know is solid and then start troubleshooting the anomalies in that, rather than always reinventing the whole wheel every single time you encounter a new troubleshooting issue. So let's review, fly by review of the CCNP. We looked at what the CNNP was all about, three exams,


all that kind of stuff. Just again, fly by review. More on that, check out the other CCNP series. We saw Bob and Carl. Bob being who I currently am and Carl who I aspire to be, somebody with a plan in mind. And then finally, we looked at successful network


maintenance. What are some of the keys to maintaining your network and then as we go on in the series, I'll expand those out, unpack those, so you'll be able to see what is the meat inside of that. But for now, I have to check that voicemail. I hope this has

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

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