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

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

00:00:00

Layer 3 connectivity and EIGRP part 2. Ok, part 1 we took out scenario 1, the server room fire. Our network is backup and working again. So now we can look at scenario 2, the CCTV implementation and figure out that whole story is all about, and we'll also squeeze the internet access failure. But judging from how long

00:00:19

these are taking; this will probably be a one scenario per nugget system, but for now. Let's get started. Al right, scenario 2 CCTV, so we've got a company testing a closed circuit television solution, so basically an IP camera solution, it sounds like. New CCTV

00:00:41

VLANs have been created at each site. The CCTV vendor arrives tomorrow to install, so it looks like you're going to have cameras at the branch and the headquarters. Before the vendor arrives, you must test connectivity and make sure the device on the branch CCTV VLAN reaches the devices on the headquarters' CCTV VLAN.

00:01:02

Says, you may move client 1, HQ, to the CCTV VLAN, for testing, so this guy can, oops, wrong button. This guy can kind of be our test client to throw into the CCTV VLAN. CCTV, sorry, I keep saying that, CLT2 has already been moved into the CCTV VLAN. Wanna see something? Check this out, I want to show you something. It's a project plan for VLAN configuration, so this

00:01:35

my scenario 2 project plan, and, honestly, when I put this together, I struggled, because, after the last nugget, and doing the troubleshooting, and remember, where the CRL 1 and 2, configs were switched, and I just, by the time it got sent down, I just, got lost as to where I even was, I was like ah! I need a project plan. And so

00:01:51

I created this, as I read through the scenario thing, and ok this will be my project plan, this will be good to follow, it's a good practice, but I was thinking: "You know what, for the t-shoot exam, you don't have excel, you've got some paper where you can write some notes, but you're not going to make a spreadsheet for you, you're not going to even make a list of steps. "Ah!

00:02:10

such a dilemma because Cisco wants you, in the exam environment, to use your intuition, to kind of work your way through it, figure it out, and so on, but of course in the t-shoot learning what they want you to gather from preparing for the exam is that, you know what, shooting from the hip, like I was doing in, well every nugget until now. It's not the best practice,

00:02:36

you wanna create a project plan, and then so, you have kind of this real world environment. This is what you should do in the real world, and I'll walk through it, versus, what you should do in the exam environment, which you don't have excel, you can't make a project plan at all with that kind of stuff. I guess you

00:02:50

could make a rudimentary one, so I kind of struggled. So I have to, moving forward, I'd like to use this project plan, just for scenario 2, and let's see how it goes, but I'm not too sure if I'm going to do this for every single one because I'm thinking: "You know not that it takes a lot of time, but it takes some time, and in the exam environment, which is what I'm trying to prepare you for, a lot of times you just don't have the time to do all this," but I guess it will give a good thought process.

00:03:15

You see my dilemma; you see why I'm going back and forward on this, so here's what my thought was. Ok, based on this, branch switch 1, we have to verify VLAN 29 creation, so make sure that's created over there. Make sure client 3 is in the correct VLAN, and then verify the trunk configuration between VRL1, VRL2 and BSW1. In the, as I was writing that, all of a sudden popped and it occurred on my mind that, funny when I actually opened the lab. Oh yeah! Based on scenario 1, we had a fire that took out the comm server for the branch office. That was the strange thing,

00:03:50

right?, a fire in the headquarters took out the comm server. So we can't access that; so my thought is: "Should we verify it?" Maybe, maybe I'll work on the headquarters stuff first, you know, and we I say should we verify it, what I'm thinking is telnet over to BRO1 from CRO1 and see if I can telnet to BSW1, but we haven't even tested that yet. So we can see if telnet

00:04:14

till save the day and allow us to see some of the config over there; actually you know what, well no, I was gonna say, I have a remote desktop connectivity to client 3, so maybe that would be a good starting point. So, anyway, just some thoughts, so we have BRO1 and BRO2 verify their sub-interface configuration because they're gonna need that new sub-interface, hang on let me go back here, they're gonna need that VLAN 29 sub-interfaces if it's gonna route correctly.

00:04:39

CSW1 and CSW2, ASW1 so this little cluster of switches over here, I'm going to verify we've created VLAN 115, which is CCTV for the headquarters, and then verify the trunks make sure it's passing, on all the trunks, going between these switches. We'll move on

00:04:55

ASW1, move client one to the CCTV VLAN, and then I've got my questions, I mean, the scenario did not tell us that a new subnet had been created, or DHCP pool assigned, so it's going to, so we'll kind of work our way through it. We'll move him to VLAN 115, and then just hopes he magically gets an IP address as that would mean an administrator, previously, had figured that DHCP pool either on CSW1 or CSW2 or who knows, who knows where the DHCP service is, but it would have been previously configured.

00:05:28

So, let's see, where to being? I know I kind of put this in the order I was thinking, but I'm thinking now, to begin on client 3. Simply because I want to just see because they said client 3 had already been moved. I wanna see if it has an IP address, if it does, then that would be subnet that we may wanna use for that, and then we'll kind of pick up from there and work through these guys. So, ok,

00:05:53

so let's jump over to client 3. I opened up this little remote desktop session before because it takes a little while to get them open. So I'm just going to go to command prompt; do an ipconfig or an icpconfig. Alright, so we got nothing. Ok, so if this guy has nothing, ok here's my thought process, if he's got nothing then either a) we got an issue with BRO1 not handing IP addresses correctly as in the trunking is incorrect or b) they have just haven't created a subnet for it yet, and at that point, it would be up to us, up to us completely, to create a subnet for CCTV, which should be fine. And would say, just for

00:06:44

this, we're just testing, we have no idea if they need DHCP, for the real solution, and nor what is told to us that it needed DHCP; so I would just say, we'll create a subnet, we'll statically assign the addresses, but let's check, let's check a few other things first. I'm going to bring up my connection to CRO2 and telnet over to BRO1 because I remember he was the DHCP server. So let's do a show CDP neighbor, alright, so let's do entry BRO1, I keep doing that, ok, capital O. So we got BRO1 is this IP address, so let's just hop over there. Copy, paste, enter and username, admin, cisco ok so let's

00:07:33

get in privileged mode here and do a show CDP name. So we've kind of hop over there, so, ok, that's not good, I don't see the switch, so let's do a show IP interface brief, and let's see if we've got any status on the switch. Ok, we've got fast Ethernet0; looks like it's going to the switch, look at this, we've got this 29, which I'm assuming is matching up to this VLAN 29 that they created for CCTV, so let's do a show run interface FAA0.29. What's up with that, ok, so, why would you do that? Interesting, ok, so we've got, we've got this, so let me do a little documenting here. I'm using my project plan, right, so I'm gonna grab that

00:08:34

guy and paste him into there. So we've got BR01, I'm verifying sub-interface configs, so BRO1 is this IP address which means his subnet range, C.192, it would be an increment of 64. So it would be 128, right, so we've got, we've got 0 through 64, first one, 65 through 128 is the next one, so essentially this is the range. So we've got

00:09:02

a range of .65 through 127. So 127 is the broadcast address, 65 is the network ID. Are you following me, I'm just kind of subnetting in my head right here. So this guy 126 is the last valid IP address from that, so before we even fix that VLAN tag let's see, actually, I'm going to document that too. This is FA0/0.29, so let's also document that, BRO, let's just well, space, so he's got a .1 q tag of, what was that, 8 13, is that what it was? Yeah, 8 13, so that's gotta be wrong, so let's fix that right now right? Interface FA0/0.29 because it said clearly the guy was in VLAN 29, so, dot, encapsulation and .1 q 29. Alright, we fixed that, let's go back and verify it, we've got the right VLAN. Let's do a run section DHCP, that's going to

00:10:14

take a little while because this is our old 2600 router, so meanwhile, let's think this through, so that's been fixed, let me erase that, because it's in the right VLAN. Let's look at BRO2, you cool with that? Ok, so there is not DHCP pool configured, and like I said, I'm not gonna set one up, simply because, we don't, well I guess now we know the subnet, but it was not required of us to setup DHCP, so I'm not giving them any extra consulting time for free, right, I'm going to statically assign those PCs, an IP address from the subnet, use this guy as the default gateway, as a matter of fact, they didn't even setup, GLBP or HSRP on that interface, so let's see, let's do that, let's check out BRO2. Show CDP neighbor, so BRO2 we're seeing him on here, do they have, I wonder if they have mirrored interfaces configured, or something to that effect, I'm just gonna stick with these. It looks like they have redundant

00:11:22

interfaces going to the same place both using the same frame relay cloud. I'm guessing one is maybe multipoint, the other one is point to point; we'll worry about that later. So let's do a show CDP entry BRO2 asterisk, so we got .14 which is BRO2, let's hop over there. Cisco, let's do

00:11:49

show IP interface brief see if he's got a .29 interface. He doesn't, so BRO2 you are out of the picture, quit, go ahead. Ok, the reason why, again, this is a test, they did not tell us set up HSRP or GLBP or any redundancy at all, so we're just testing. We're truly testing client 3 through BRO1, we've got, hang on, let me clear up my notes here. So we know the subnet

00:12:20

is going to be 10.1.164., what would that be, 65 through 127, default gateway needs to be .126. I should be documenting this on my spreadsheet, right, so here's what I'm going to do. I'm going to over to client 3, and let's give him the IP address, static IP, 10.1.64., sure, let's say, let's make him 70, just because I'm figuring there's nothing at that IP address. A wise man would ping that before and test it, but

00:13:02

I'm not going to, so we're going to do, here's the subnet mask, 255.255.255.192, right, there we go, so let's shoot over to the client 3, where did he go? Here we go, alright, and let's give him the IP address, so let's make sure he can ping through to that router.

00:13:23

See that wasn't on my project plan spreadsheet; it's part of the discovery process, so control panel, network and internet, do guys like the classic view? I like classic view so much better. The friendly view just gives you way too many clicks. Alright, so lab, we're right there, then we go to properties, alt enter, and let's give him his IP address, so we've got 10.1.164.70, 255.255.255.192, default gateway 10., I'm looking at my spreadsheet right next to me, so 164.126 which is our BRO1, so let's hit ok on that guy. Let's bring up our command prompt, as our, our Windows XP must be a virtualized XP which they have like 2 megabytes of RAM to, it's like a Sputnik satellite, c'mon, let's move along. 10.1.164.126, alright, what are you doing here to me, no, so I guess that reveals a few things, we've got an issue going on with that switch, and that's, honestly, that's to be expected, because when I did a show CDP neighbors, hang on where am I?, 01 CRO1 right?, when I did show, yes, when I did a show CDP neighbors, on, where did my telnet session go?, Ok, I was over here, I was on CRO2, so when I did a show CDP, I will finish my statement, show CDP names on BRO1 is not seeing the branch switch, that concerned me before, let's a show run interface FA0/0. Ok, and so it's showing that is connected there, let's do a show CDP interface, and let's just make sure CDP is indeed running, yeah we've got CDP running on FA0/0, so we should be seeing that guy, so what I'm going to do, let's take the backdoor in, let's go to CRO2, sorry, let's go to here BRO2, follow me, I'm going to go here because I just went to here, and I'm not seeing it, via switch CWS1, so I'm gonna go to BRO2 and do a show CDP neighbors, and let's see if BSW1 shows up at that point, right. So let's see, I just was telnetted

00:16:02

to him, so let's get back there, admin, Cisco, so now I'm on BRO2. Show CDP neighbors, this is a challenge, alright, so let's, let's see, we're seeing 01 02 that's fine, show run interface FA0/0. Ok, we've got the connection to branch switch 1, this should work right, hang on, let me think about this, alright, neither BRO1 or BRO2 can see BSW1 via CDP, now there's a chance CDP can be disabled on BSW1, so we can go with that, maybe that's part of the challenge, we did this, we made, we changed the tag on this, it was, what was it, 8 13, that was the original tag on here, we changed it to 29 because we assigned, no, it had an IP address from the right subnet. We've got this guy that's now statically assigned to

00:17:15

that subnet, he's supposed to be VLAN 29, but we can't verify that. You know what let's do this, let's, I'm gonna put the tag back to 8 13 on this because what if they made that guy a member of 8 13 because if we do, and he can ping, then I mean well, we can say that, we can test it, but this will have to be 8 13 because we have not access to BSW1, we don't know how to get there. We don't have its IP address, so,

00:17:42

let's do that, you're with me on that? Ok, so let's jump over to, let's do, where was I, zero, ok I'm on BRO2 I'm going to exit back out show sessions, show sessions. So I've got BRO1, I'm going to hop back there, and let's do, try, a show IP interface brief, we've got the .29 interface, and I want to make sure, because I subnetted that in my head, it's the right subnet right? Show run interface FA0/0.29, I don't want to doubt myself here, but I am. So I'm going to,

00:18:24

so we've got 10.1.164.126, 192, that would an increment of 64, so 0 through 63, 64 through 128, yeah that's right, that's gotta be right, so that's the last valid address from that second subnet, and I assigned the IP address correctly in here correctly right? 164.70 right?, wow, no, yes, no, yes, so ok, so it's 160, so I was thinking I did that wrong, so 160, 1.164.70, right subnet mask, right default gateway, ok so that's good, so let's do that, let's change the tag back to, what was it?, 8 13, let's verify it.

00:19:21

So it was 8 13, right there, so let's go into FA0/0.29, and let's plaster that guy in there, let's see what happens. I'm gonna jump back over here, it's gonna take a moment for that to take effect, so I'm just going to do a dash t. Oh, look at that, look at that, you see that happening, alright, so, so here's the deal. Here's the deal,

00:19:55

I want my money back. They're saying, hang on; I gotta look at the instructions again. Yeah, I'm looking at the instructions here; let me bring it over so that you can see it. Official instructions here, take a look, we've got preparation for CCTV pilot, one thing I did forget is I forgot to put the VLAN subnet, so it did tell us the subnet, and they said ok VLAN 115 on this subnet, so, I'm just going to, I'm gonna copy that bad boy, put it on my excel spreadsheet.

00:20:25

Alright, so we've got that, let's just, yeah, that's fine. We've got that taken, so they did give us the subnet, but look at that, they said VLAN 29, I did that correctly, and then, we're, we're, it's VLAN 8 13, I'd be like happy to fix it for them, but we don't get access to BSW1, it's an invisible switch, and it's, if I remember right in previous exercises, I remember the branch admins are like: "hey don't touch our switches, not in your capability," so, so I guess what we'll do is, we'll go with it, we'll leave this, we'll kind of make the documentation update, and say ok this is not 29 it's 8 13, and sorry, but I don't have the ability to change it. So we'll leave the trunk at 8 15, we know that this guy is assigned to 8 13, excuse, because he is able to ping out, so now let's jump over and let's verify this side of things, so let me bring up each one of those configuration windows.

00:21:26

Alright, I've got my switch connections brought up out here, so hang on, let me bring my spreadsheet, look at this project plan, I'm like whatever I'm going after it, so, so here's my thought, let's start on this side, we're going to go with VLAN 115 because that's what they said, and they said VLAN 115 it's going to be this subnet, so that subnet needs to route, needs to communicate, with well, again let's rectify this, this is VLAN 8 13, over on the branch side, and on this subnet, I gotta turn word wrap on, where is word wrap, nah, it's not important. Oh but it bothers me,

00:22:09

isn't there a quick key for that? Then maybe I just, oh, there it is, I just had to find it. So we've got the branch office 8 13, so, we'll just say branch is good, branch is good to go; although, we do will want to make sure that subnet is being routed, so you know what, before we leave the branch, I want to make sure EIGRP is advertising that subnet to the other side because that would totally be a scandalous thing to do, and would cause everything to be unreachable, so let me get, let me get over here. So BRO1, he's advertising that subnet, let's do a show run interface FA0/0.show 29, oops, 29, alright there's the subnet, so let's do show run section EIGRP, alright and that's going to take a moment so, while we're doing that, I'm also going to flip over to, see I brought over a connection to ASW1, so where is he? ASW1, yeah I got it, so meanwhile, we've got, let's see passive interface, no passive interface, in that case that's fine, we can keep the interface passive because we don't need, we're not needing to send EIGRP advertisements out that interface we just need to make sure that subnet, this subnet, right here is being advertised to the rest of the network so people know about it, so let's look, do we have a .126 in our list, no, I'm glad we checked, now let's go into router EIGRP 1, EIGRP 1, and we'll do a network 10.164.26, 0.0.0.0, specifically that interface, so now we are including this subnet in the route advertisements to the rest of the world, which is good, I'm gonna just do a show, well, yeah, I know EIGRP is doing neighbors from the last exercise, show EIGRP neighbors make sure I got neighbors with the other guys, and we do, so we're seeing our relationships form with our 2 CROs routers on the other side, so let's do this, what I'm gonna do, I'm going to say the branch is done, you're good with that? We got branch advertising that subnet, should be, let's, you know what, hey, before we do that, let's go the CROs, and let's do a show IP route, let's make sure we see that subnet showing up.

00:24:37

Alright, we got load balancing heaven here, not concerned with all those, ok, here we go, we've got some serial links, so why am I doing this?, let's do show IP route, let's type in a specific IP address 10.1.160., let's do, what was it, 64, the subnet, so ok, so it's that, we are learning it, via, it looks like neighbor on the frame relay cloud, so this is good. We've got the network being advertised

00:25:11

,ok, so let's shoot over to the ASW1, I'm going to start the closest to the client, so I just want to make sure that VLAN 115 exists, you know because again, from the lab they said somebody started the config, but didn't finish, so let's do a show VLAN and make sure we've got VLAN 115, so good, we've got VLAN 115, let's put our client into it, so client 1, let's do a show interface description and we've got link to client 1 FA0/8, so let's go interface FA0/8, switchboard access VLAN 115 you are moved, so we've got, now do a show VLAN make sure it looks kosher, there it is. Ok, so we've got, it looks like he's attached to

00:26:02

a IP phone as well, which is cool, we can go with that, and we've got him on VLAN 115, so meanwhile, you know, I'm starting from the edge out so let's go over to client 1, where is he? That's this guy when I open the remote desktop session I just open the command prompt and say you are client 1 because I want to remember which one is which. So let's do an ipconfig, he may have his

00:26:29

old IP address, yeah, let's do an ipconfig release, in fact I know, I know they don't have a DHCP scope, I don't know that, so I'm gonna do an ipconfig renew, I was going to say I know they don't have one for VLAN 115 because they didn't on the other side, so the chances are we're not going to get an address, yeah, I'm not going to wait, I know they don't have a DHCP scope configured, so let's statically configure this guy.

00:26:55

Alright, going into our lab, acquiring network address, let's just break out of that, because sometimes it takes forever to do anything, so we're gonna go to TCP/IP and subnet on this side, again we were, here let me bring it up, it said the VLAN 115 subnet would be 155.0 /24. Ok, so we're gonna do, let's just, I'm going to pick a random address. Let's do a.hundred, right, you're good with that, let's

00:27:29

do client 1 static IP address 10.1.155.1 hundred and his subnet mask will be this, so we got those guys documented, so that way I'll be able to test pings between them. So we've got 10.1.155.100, 255.255.255.0, 10.1.55., are you good with?, let's do 254, and the only reason I'm doing that is because the other side was 126, it was the last IP address from that subnet, so I'm gonna assume, I'm assuming a lot, that they're consistent.

00:28:09

Of course, we'll verify that and if the default gateway is not 254 we can come back and change it, so ok good, so we click ok on that, and so, he's good, ipconfig, got the IP address, I'm just curious. Let's do that ping 10.1.155.254, yeah I didn't think so. Let's move that out of the picture, I

00:28:37

just want to see if I can ping the default gateway, I'm gonna move back to ASW1 because again one of my project plans was not only to move, I'll just put complete on this guy, I've move client 1 to CCTV VLAN, I'm gonna verify his trunk configuration, so let's do a show interface trunk, let me make sure VLAN 115 has been added to the right guys, so it looks like we are on port channel 1, we've got 115 that has been added. So let's look here, port channel 1, which one is that, let's do a, let's do a show route, let's just check the running config, so we've got out VLANs, we've got port channel 1, so this the one to CSW1, it's got 115, is that a port channel? I guess it is, ok, so fast Ethernet 0/1 and 0/2 are going up there, which is cool, that's cool, I just only had one line, so I've must have missed the second link when I drew that diagram, then that's fine, so we've got PO1, which VLAN 115, checked, we're verified. On ASW1, is that on the port channel? so my guess is again, this is a test, I'm not going to do HSRP, I'm not going to add in both sides and route the interface and all that, I want to, I want to make client 3 ping client 1 on those two different subnets, and that's the end of the story, so I'm not going to go above and beyond on this config, if they only added it to this port channel, I'm going to follow their lead, and we're going to the get the ping going this route to CRO1, you're good with that? Alright, so let's go to, let me find them, CSW1, so let's go to the core switch and do the same thing; show the VLANs and just make sure that we've got VLAN 115. Now we're going to have to go above and beyond on this guy, ok CCTV, so we've got the VLAN, right there, let's check his trunk, let's do a show, show interface trunk, let's make sure that 115 is indeed added, it is, to port channel 1, it's not pruned, so I would say, you know at this point let me go back to my project plan, I'm gonna say this guy is complete because CSW2 is no longer in the picture; I don't care about him in anything because he's not part of the story. We've got

00:31:03

a complete there; I'm going to do a show, let's do show run interface VLAN 115, ok, nice, pick the random IP address, I'm guessing when they set this up, that we're gonna have this setup for HSRP or something so maybe core switch 1 would be 252, core switch 2 would be 253, and then the HSRP shared address would be .254, but again, that you know what, I'm going to verify, I'm gonna bring up the documentation, I want to make sure I didn't miss anything on the exercise instruction, they did not want us to setup, ok. Company is interested, blah,

00:31:38

blah, blah, headquarters, branch, to keep the traffic separated CCTV solution, ok so, tomorrow, they just said, two new VLANs, one the vendor will come in and install the system. Ensure your VLANs have been created and there's an IP connectivity between them, good. Your team has been very busy, so this last, so this

00:31:55

step was not done until yesterday afternoon your colleague had implemented VLANs while handling other tasks but did not have time to test. You were asked to verify, so your task is to verify and ensure there's IP connectivity between the two VLANs, right, you're not, are you reading the same thing I'm reading? like there is nothing telling us to setup HSRP, it just says make them reachable, so that's what I'm gonna do, let me go over here to, I'm gonna go back to our client guy, let's see where he is, client 3, and change his default gateway to 252 because that will let us get to core switch 1 as our default; we can then test the ping, and man, we can even go further, we can test end to end connectivity and see if we're there because if that's all there is to it, then great, so I'm now pinging my new gateway too, so good, I'm reaching it.

00:32:56

Let's go for it all, let's go back to our Excel spreadsheet, client, here's my Excel spreadsheet, client, VLAN 115, branch office, so ok, so client 3 in the branch office is this IP address, copy, that's completed back over here, paste, I'm pinging, hey, I'm not gonna argue with that right?, so let's do a traceroute -d and paste it into there as well, I wanna make sure, dash d, if you haven't done it before, doesn't resolve the hostname, otherwise it takes like 30 seconds for every hop, it's painful, so we're going to 252, this guy is shooting us to .6, which I'm assuming is one of the CROs, one of the CRO routers, CRO router 1 shoots it to CRO router 2 or I'm not too sure why we're jumping a couple times, but we're getting right here, that's our branch office, this router here, and then our branch office router gets it to the host, so I would say, and I hope you're with me, we've moved the two hopes that both of those guys are tested and approved, we are now pinging fully between client 1 and client 3. Alright, let's do a little debrief, I have to admit I was anxious to see the solution, so I hope in the solution, I was like, is that right? Did I get it? I was like, and as soon as I saw the solution I went like: "ahhh! Are you kidding me? So I looked at the troubleshooting ticket, so first off, you might remember from the last one, I told you I reversed the scenarios because the server room fire is obviously, has to be fixed, so this trouble ticket was listed before the server room fire, so there's saying hey by the way nothing will work until you fix the server room fire, which they call trouble ticket I, I call it trouble scenario 1, so once you've fixed the server room from fire, then all you have to do to get this scenario working is change the IP address, on the fast Ethernet 0/0.29 sub-interface on BRO1, and I looked at that, and I was like what oh!, let come back here to our scenario, see that, I know it's kind of goofed up right now, but originally when we came in here, I documented the IP address of BRO1 as 164.126, and so what I did is I said: "ok of that's the subnet then let's make the client be a part of that subnet" I gave him the .70 address, you remember all this, that's where I came up with this, but I failed to look at the instructions where it says, you know the branch office VLAN, and it should be .163.64, I should be using this subnet, so if you take a look, it was configured as .164, and they're saying that subnet should have been .1.163, as the subnet, now, they didn't mention anything in the solution about this VLAN 8 13, so, my guess it's just a nil error, they didn't use the right VLAN number. They didn't use 29 as the VLAN, so, so in my mind that cancels that out then, so here's what would have happened, let me just show you this, jump over to, bring up my correct router, jump over to BRO1, as soon as I saw this switch I was like ah! you're kidding me, and then I looked, and if you look under EIGRP they had a network statement of .160.0 with this funky wild card mask, which would actually be the range, you know, 10.1.1.60 through 163 on that third one, so if I would have changed the subnet right here to .163 from .164 then I would not have had to add this network statement to advertise this subnet, it would have just automatically be advertised because that one was in there to advertise it, but I threw my hands in the air, and I said: "we got a working solution," we got the wrong subnet number, but I would say yes, if that were an exam environment, oops! Clicked the wrong button, I would have left a comment about that VLAN 29, VLAN.8 13, but yeah, I would definitely not be able to argue. They would have said:

00:37:04

"hey, we told you in the required features there that it should have been .163; and you configured it for .164," so what else can I say? We solved scenario 2, one way or the other. For now, I hope this has been informative for you, and I'd like to thank you for viewing.

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: BGP

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

COURSE RATING

Basic Plan Features


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

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

Notes
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.

NuggetLab
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