Troubleshooting Cisco Networks: IPv4 Routing Protocols for CCNP R&S 300-135 TSHOOT

Course Overview
Hi everyone. I'm Ben Piper, independent IT consultant and published author, and welcome to my course, Troubleshooting Cisco Networks: IPv4 Routing Protocols for CCNP Routing and Switching. In this course you're going to tackle 16 different troubleshooting tickets covering complex IPv4 routing problems involving OSPF, EIGRP, and redistribution. This is the second course in a six course series designed to prepare you for the Cisco CCNP TSHOOT exam, troubleshooting and maintaining Cisco IP networks, which is part of the CCNP routing and switching track. By the end of this course you'll have the confidence to approach any IPv4 routing or redistribution problem, no matter how complex the problem or the topology, you'll be able to determine where to start, how to narrow down the problem to a layer, and even how to figure out what specific technology is causing it. I hope you'll join me on this journey to learn Cisco network troubleshooting with this course, Troubleshooting Cisco Networks: IPv4 Routing Protocols for CCNP Routing and Switching, only here on Pluralsight.

Lab Setup
In this module you're going to walk through the lab setup for this course. The process is mostly the same as in the first course, but there are a few differences. First, you're going to import the course topology into VIRL. The topology for this course is different than the topology for the first course, but please don't think, oh, I've already got the topology imported, I'm ready to go. No. Although the physical topology looks the same in VM Maestro, under the hood it completely different. After that I'm going to show you how to save your device configurations in VIRL, which is something we did not cover in the last course, and finally, you'll get acquainted with the layer 2 and layer 3 topology diagrams for this course. Let's get started. If you haven't already, go ahead and boot up your VIRL server. You don't need to pause the video, just start the boot process, and keep watching. I want to make you aware that I'm running VIRL version 1. 2. 64 with IOS 15. 6. 2. T on the routers, and 15. 2. 4055 on the switches. Please understand that I am not saying that you need to be running these exact versions. In fact, even if you're running earlier versions of VIRL or IOS do not upgrade them, at least not yet. Follow along with the course, and if you run into any problems leave me a note on the course discussion page. In this course you're going to run into a lot of broken configurations, and that's by design. Chances are any problems you run into are not bugs in VIRL or IOS. However, if it turns out to be an IOS or a VIRL problem, then you can consider upgrading. Upgrading VIRL is not like updating an app on your smartphone. It's a monster, and if something goes wrong it can completely break your installation, and if that happens you'll have to start over from scratch, so avoid upgrading unless there is a specific bug fix or new feature that you need.

Troubleshooting EIGRP Adjacencies
In this module, you're going to tackle three trouble tickets that are related in some way to problems with EIGRP adjacencies, as you probably guessed. I'm going to dispense with the normal module introduction because from this point on we're going to be simulating the TSHOOT exam. That means that while I am going to think out loud and walk you through the troubleshooting steps, I'm not going to spend time delving into detailed explanations. Instead, I'm going to refer you to my course, Implementing EIGRP for CCNP Routing and Switching 300-101 ROUTE. Before we get to the tickets in OSPF and redistribution I'm going to refer you to the relevant courses for those topics as well. Treating the labs in this course like the actual TSHOOT exam means tracking your time because you have only 120 minutes for the exam. At the end of this module we'll see how long it will have taken to complete those first three tickets. The goal is to take between 5 and 8 minutes per problem on average. That's not 5 to 8 minutes to solve the problem, that's 5 to 8 minutes to read the ticket, diagnose the cause or causes, solve the problem, and fully verify your solution. I'm not going to sugar coat it. That's challenging, but it's very, very doable. Alright? Are you ready? Let's get started.