Are you sure you want to cancel your subscription?

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

Sorry to see you go

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

Are you sure you want to reactivate?
Welcome Back!

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

Reactivate Subscription

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

Your Subscription term is from - .

Questions? Call Sales.

541-284-5522
Payment Due:

OK
Auto-Renew Subscription

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

Click continue to set up your payments.

CBT Nuggets License Agreement


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


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


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

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

Billing Agreement


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

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

Cisco CCNP TSHOOT 642-832

Route TSHOOT: L3 Connectivity and EIGRP, Part 2

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

A free trial includes:

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

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
00:00:05 - scenario 1, the server room fire. Our network is backup and working
00:00:08 - again. So now we can look at scenario 2, the CCTV implementation
00:00:12 - and figure out that whole story is all about, and we'll also
00:00:15 - 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
00:00:23 - system, but for now. Let's get started.
00:00:26 - Al right, scenario 2 CCTV,
00:00:31 - so we've got a company testing a closed circuit television solution,
00:00:37 - 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
00:00:47 - tomorrow to install, so it looks like you're going to have cameras
00:00:49 - at the branch and the headquarters. Before the vendor arrives,
00:00:52 - you must test connectivity and make sure the device on the branch
00:00:56 - CCTV VLAN reaches the devices on the headquarters' CCTV VLAN.
00:01:02 - Says, you may move client 1, HQ,
00:01:05 - to the CCTV VLAN, for testing, so this guy can, oops,
00:01:10 - wrong button. This guy can kind of be our test client to throw
00:01:14 - into the CCTV VLAN. CCTV, sorry, I keep saying that, CLT2 has
00:01:20 - already been moved into the CCTV VLAN.
00:01:23 - Wanna see something?
00:01:26 - Check this out, I want to show you
00:01:30 - 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,
00:01:38 - I struggled, because, after the last nugget, and doing the troubleshooting,
00:01:42 - and remember, where the CRL 1 and 2, configs were switched, and
00:01:46 - I just, by the time it got sent down, I just, got lost as to
00:01:49 - 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
00:01:54 - this will be my project plan, this will be good to follow, it's
00:01:57 - a good practice, but I was thinking: "You know what, for the
00:01:59 - t-shoot exam, you don't have excel, you've got some paper where
00:02:05 - you can write some notes, but you're not going to make a spreadsheet
00:02:08 - 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,
00:02:17 - to use your intuition, to kind of work your way through it, figure
00:02:21 - it out, and so on, but of course in the t-shoot
00:02:26 - learning what they want you to gather from preparing for the
00:02:30 - exam is that, you know what, shooting from the hip, like I was
00:02:32 - 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
00:02:39 - this real world environment. This is what you should do in the
00:02:42 - real world, and I'll walk through it, versus, what you should
00:02:45 - do in the exam environment, which you don't have excel, you can't
00:02:48 - 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
00:02:54 - to, moving forward, I'd like to use this project plan, just for
00:02:57 - scenario 2, and let's see how it goes, but I'm not too sure if
00:03:01 - I'm going to do this for every single one because I'm thinking:
00:03:02 - "You know not that it takes a lot of time, but it takes some
00:03:06 - time, and in the exam environment, which is what I'm trying to
00:03:09 - prepare you for, a lot of times you just don't have the time
00:03:12 - 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
00:03:17 - this, so here's what my thought was. Ok, based on this, branch
00:03:21 - switch 1, we have to verify VLAN 29 creation, so make sure that's
00:03:25 - created over there. Make sure client 3 is in the correct VLAN,
00:03:30 - and then verify the trunk configuration between VRL1, VRL2 and
00:03:36 - BSW1. In the, as I was writing that, all of a sudden popped and
00:03:40 - it occurred on my mind that, funny when I actually opened the
00:03:42 - lab. Oh yeah! Based on scenario 1, we had a fire that took out
00:03:47 - 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.
00:03:54 - So we can't access that; so my thought is: "Should we verify
00:04:00 - it?" Maybe, maybe I'll work on the headquarters stuff first,
00:04:04 - you know, and we I say should we verify it, what I'm thinking
00:04:06 - is telnet over to BRO1 from CRO1 and see if I can telnet to BSW1,
00:04:11 - 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
00:04:17 - there; actually you know what, well no, I was gonna say, I have
00:04:21 - a remote desktop connectivity to client 3, so maybe that would
00:04:23 - be a good starting point. So, anyway, just some thoughts, so
00:04:27 - we have BRO1 and BRO2 verify their sub-interface configuration
00:04:31 - because they're gonna need that new sub-interface, hang on let
00:04:33 - me go back here, they're gonna need that VLAN 29 sub-interfaces
00:04:36 - if it's gonna route correctly.
00:04:39 - CSW1 and CSW2, ASW1 so this little cluster of switches over here,
00:04:43 - I'm going to verify we've created VLAN 115, which is CCTV for
00:04:47 - the headquarters, and then verify the trunks make sure it's passing,
00:04:50 - 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
00:05:00 - questions, I mean, the scenario did not tell us that a new subnet
00:05:03 - had been created, or DHCP pool assigned, so it's going to, so
00:05:08 - we'll kind of work our way through it. We'll move him to VLAN
00:05:11 - 115, and then just hopes he magically gets an IP address as that
00:05:15 - would mean an administrator, previously, had figured that DHCP
00:05:21 - pool either on CSW1 or CSW2 or who knows, who knows where the
00:05:26 - 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
00:05:32 - order I was thinking, but I'm thinking now, to begin on client
00:05:37 - 3. Simply because I want to just see because they said client
00:05:40 - 3 had already been moved. I wanna see if it has an IP address,
00:05:43 - if it does, then that would be subnet that we may wanna use for
00:05:46 - that, and then we'll kind of pick up from there and work through
00:05:50 - these guys. So, ok,
00:05:53 - so let's jump over to client
00:05:56 - 3. I opened up this little remote desktop session before because
00:06:00 - it takes a little while to get them open. So I'm just going to
00:06:04 - go to command prompt; do an ipconfig or an icpconfig.
00:06:10 - Alright, so we got nothing.
00:06:14 - Ok, so
00:06:16 - if this guy has nothing, ok here's my thought process, if he's
00:06:20 - got nothing then either a) we got an issue with BRO1 not handing
00:06:26 - IP addresses correctly as in the trunking is incorrect or b)
00:06:31 - they have just haven't created a subnet for it yet, and at that
00:06:34 - point, it would be up to us, up to us completely, to create a
00:06:38 - 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,
00:06:48 - for the real solution, and nor what is told to us that it needed
00:06:51 - DHCP; so I would just say, we'll create a subnet, we'll statically
00:06:54 - assign the addresses, but let's check, let's check a few other
00:06:57 - things first. I'm going to bring up my connection to CRO2 and
00:07:02 - telnet over to BRO1 because I remember he was the DHCP server.
00:07:08 - So let's do a show CDP neighbor,
00:07:12 - alright, so let's do entry BRO1, I keep doing that, ok, capital
00:07:20 - O. So we got BRO1 is this IP address, so let's just hop over
00:07:26 - 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
00:07:36 - kind of hop over there, so, ok, that's not good, I don't see
00:07:41 - the switch, so let's do a show IP interface brief, and let's
00:07:45 - see if we've got any status on the switch. Ok, we've got fast
00:07:50 - Ethernet0; looks like it's going to the switch, look at this,
00:07:55 - we've got this 29, which I'm assuming is matching up to this
00:07:59 - VLAN 29 that they created for CCTV,
00:08:03 - so let's do a show run interface
00:08:06 - FAA0.29. What's up with that, ok, so, why would you do that?
00:08:19 - Interesting, ok, so
00:08:22 - we've got, we've got this, so let me do a little documenting
00:08:29 - 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
00:08:38 - sub-interface configs, so BRO1
00:08:41 - is this IP address which means his subnet range, C.192, it would
00:08:46 - be an increment of 64. So it would be 128,
00:08:50 - right, so
00:08:52 - we've got, we've got 0 through 64, first one, 65 through 128
00:08:58 - is the next one, so essentially this is the range. So we've got
00:09:02 - a range of .65
00:09:04 - through 127.
00:09:08 - So 127 is the broadcast address, 65 is the network ID. Are you
00:09:13 - following me, I'm just kind of subnetting in my head right here.
00:09:15 - So this guy 126 is the last valid IP address from that, so before
00:09:21 - we even fix that VLAN tag let's see, actually, I'm going to document
00:09:28 - that too. This is FA0/0.29,
00:09:32 - so let's also document that, BRO, let's just well,
00:09:38 - space, so he's got a .1 q tag
00:09:43 - of, what was that, 8 13, is that what it was? Yeah, 8 13, so
00:09:48 - that's gotta be wrong, so let's fix that right now right? Interface
00:09:52 - FA0/0.29 because it said clearly the guy was in VLAN 29, so,
00:09:58 - dot, encapsulation and .1 q 29.
00:10:05 - Alright, we fixed that, let's go back and verify it, we've got
00:10:10 - 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,
00:10:18 - let's think this through, so that's been fixed, let me erase
00:10:21 - that, because it's in the right VLAN. Let's look at BRO2, you
00:10:26 - cool with that? Ok, so there is not DHCP pool configured, and
00:10:32 - like I said, I'm not gonna set one up, simply because, we don't,
00:10:36 - well I guess now we know the subnet, but it was not required
00:10:40 - of us to setup DHCP, so I'm not giving them any extra consulting
00:10:43 - time for free, right, I'm going to statically assign those PCs,
00:10:47 - an IP address from the subnet, use this guy as the default gateway,
00:10:51 - as a matter of fact, they didn't
00:10:53 - even setup, GLBP or HSRP on that interface, so let's see, let's
00:10:58 - do that, let's check out BRO2.
00:11:06 - Show CDP neighbor,
00:11:08 - so BRO2
00:11:12 - we're seeing him on here, do they have, I wonder if they have
00:11:15 - mirrored interfaces configured, or something to that effect,
00:11:19 - 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
00:11:25 - relay cloud. I'm guessing one is maybe multipoint, the other
00:11:28 - one is point to point; we'll worry about that later. So let's
00:11:31 - do a show CDP entry BRO2
00:11:36 - asterisk, so we got .14 which is BRO2,
00:11:41 - let's hop over
00:11:44 - there. Cisco, let's do
00:11:49 - show IP interface brief see if he's got a .29 interface.
00:11:54 - He doesn't, so BRO2 you are out of the picture, quit, go ahead.
00:12:00 - Ok, the reason why, again, this is a test, they did not tell
00:12:06 - us set up HSRP or GLBP or any redundancy at all, so we're just
00:12:10 - testing. We're truly testing client 3 through BRO1, we've got,
00:12:16 - hang on, let me clear up my notes here. So we know the subnet
00:12:20 - is going to
00:12:22 - be 10.1.164.,
00:12:27 - what would that be, 65 through 127,
00:12:32 - default gateway needs to be .126. I should be documenting this
00:12:36 - on my spreadsheet, right, so here's what I'm going to do. I'm
00:12:39 - going to over to client 3, and let's give him the IP address,
00:12:43 - static IP, 10.1.64.,
00:12:49 - sure, let's say, let's
00:12:53 - make him 70, just because I'm figuring there's nothing at that
00:12:58 - 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,
00:13:05 - 255.255.255.192, right,
00:13:09 - there we go, so let's shoot over to the client 3, where did he
00:13:14 - go? Here we go, alright, and let's give him the IP address, so
00:13:19 - let's make sure he can ping through to that router.
00:13:23 - See that wasn't on my project plan spreadsheet;
00:13:26 - it's part of the discovery process, so control panel, network
00:13:31 - and internet, do guys like the classic view? I like classic view
00:13:34 - so much better.
00:13:37 - The friendly view just gives you way too many clicks. Alright,
00:13:40 - so lab, we're right there,
00:13:43 - then we go to properties, alt enter,
00:13:46 - and let's give him his IP address, so we've got 10.1.164.70,
00:13:53 - 255.255.255.192, default gateway 10., I'm looking at
00:14:01 - my spreadsheet right next to me, so 164.126
00:14:06 - which is our
00:14:08 - BRO1, so let's hit ok on that guy. Let's bring up our command
00:14:13 - prompt, as our, our Windows XP must be a virtualized XP which
00:14:19 - they have like 2 megabytes of RAM to, it's like a Sputnik satellite,
00:14:24 - c'mon, let's move along. 10.1.164.126,
00:14:32 - alright, what are you doing here to me, no, so I guess that reveals
00:14:38 - a few things, we've got an issue going on with that switch, and
00:14:42 - that's, honestly, that's to be expected, because when I did a
00:14:46 - show CDP neighbors, hang on where am I?, 01 CRO1 right?, when
00:14:50 - I did show, yes, when I did a show CDP neighbors, on,
00:14:56 - where did my telnet session
00:15:01 - go?, Ok, I was over here, I was on CRO2, so when I did a show
00:15:05 - CDP, I will finish my statement, show CDP names on BRO1 is not
00:15:10 - seeing the branch switch, that concerned me before, let's a show
00:15:13 - run interface FA0/0.
00:15:16 - Ok, and so it's showing that is connected there, let's do a show
00:15:23 - CDP interface, and let's just make sure CDP is indeed running,
00:15:27 - yeah we've got CDP running on FA0/0, so we should be seeing that
00:15:33 - guy, so what I'm going to do, let's take the backdoor in, let's
00:15:36 - go to CRO2,
00:15:39 - sorry, let's go to here BRO2, follow me, I'm going to go here
00:15:45 - because I just went to here, and I'm not seeing it, via switch
00:15:49 - CWS1, so I'm gonna go to BRO2 and do a show CDP neighbors, and
00:15:52 - let's see if BSW1
00:15:55 - 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
00:16:06 - BRO2. Show CDP
00:16:11 - neighbors, this is a challenge, alright, so let's,
00:16:18 - let's see,
00:16:22 - we're seeing 01 02 that's fine,
00:16:27 - show run interface FA0/0.
00:16:32 - Ok, we've got the connection to branch switch 1,
00:16:37 - this should work right, hang on, let
00:16:41 - me think about this, alright, neither BRO1 or BRO2 can see BSW1
00:16:48 - via CDP, now there's a chance CDP can be disabled on BSW1, so
00:16:54 - we can go with that, maybe that's part of the challenge, we did
00:16:57 - this, we made, we changed the tag on this, it was, what was it,
00:17:01 - 8 13, that was the original tag on here, we changed it to 29
00:17:07 - because we assigned, no, it had an IP address from the right
00:17:10 - 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
00:17:18 - that. You know what let's do this, let's, I'm gonna put the tag
00:17:22 - back to 8 13 on this because what if they made that guy a member
00:17:27 - of 8 13 because if we do, and he can ping, then I mean well,
00:17:31 - we can say that, we can test it, but this will have to be 8 13
00:17:36 - because we have not access to BSW1, we don't know how to get
00:17:39 - there. We don't have its IP address, so,
00:17:42 - let's do that, you're with me on that?
00:17:46 - Ok, so let's jump over to,
00:17:52 - let's do, where was I, zero,
00:17:56 - ok I'm on BRO2 I'm going to exit back out show sessions,
00:18:01 - show sessions.
00:18:03 - So I've got BRO1, I'm going to hop back there, and let's do,
00:18:07 - try, a show IP interface brief, we've got the .29
00:18:12 - interface, and I want to make sure, because I subnetted that
00:18:15 - in my head, it's the right subnet right? Show run interface FA0/0.29,
00:18:21 - 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,
00:18:28 - 192, that would an increment of 64, so 0 through 63, 64 through
00:18:34 - 128, yeah that's right, that's gotta be right, so that's the
00:18:36 - last valid address from that second subnet, and I assigned the
00:18:42 - IP address correctly in here correctly right? 164.70
00:18:46 - right?, wow, no, yes, no, yes, so ok, so it's 160, so I was thinking
00:18:53 - I did that wrong, so 160, 1.164.70,
00:18:58 - right subnet mask, right default gateway, ok so that's good,
00:19:02 - so let's do that, let's change the tag back to, what was
00:19:06 - it?, 8 13, let's
00:19:12 - verify it.
00:19:21 - So it was 8 13,
00:19:24 - right there, so let's go into FA0/0.29,
00:19:29 - and let's plaster that guy in there,
00:19:33 - let's see what happens. I'm gonna jump back over here, it's gonna
00:19:37 - take a moment for that to take effect, so I'm just going to do
00:19:39 - a dash t. Oh, look at that,
00:19:44 - look at that, you see that
00:19:48 - 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
00:19:59 - the instructions again. Yeah, I'm looking at the instructions
00:20:02 - here; let me bring it over so that you can see it. Official instructions
00:20:05 - here, take a look, we've got preparation for CCTV pilot, one
00:20:09 - thing I did forget is I forgot to put the VLAN subnet, so it
00:20:13 - did tell us the subnet, and they said ok VLAN 115
00:20:16 - on this subnet, so, I'm just going to, I'm gonna copy that bad
00:20:19 - boy, put it on my excel spreadsheet.
00:20:25 - Alright, so we've got that, let's just,
00:20:29 - yeah, that's fine. We've got that taken, so they did give us
00:20:34 - the subnet, but look at that, they said VLAN 29, I did that correctly,
00:20:38 - and then, we're, we're, it's VLAN 8 13, I'd be like happy to
00:20:43 - fix it for them, but we don't get access to BSW1, it's an invisible
00:20:48 - switch, and it's, if I remember right in previous exercises,
00:20:51 - I remember the branch admins are like: "hey don't touch our switches,
00:20:54 - not in your capability,"
00:20:58 - so, so I guess what we'll do is, we'll go with it, we'll leave
00:21:02 - this, we'll kind of make the documentation update, and say ok
00:21:04 - this is not 29 it's 8 13, and sorry, but I don't have the ability
00:21:09 - to change it. So we'll leave the trunk at 8 15, we know that
00:21:12 - this guy is assigned to 8 13, excuse, because he is able to ping
00:21:16 - out, so now let's jump over and let's verify this side of things,
00:21:20 - 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,
00:21:29 - so hang on, let me bring my spreadsheet, look at this project
00:21:34 - plan, I'm like whatever I'm going after it, so, so here's my
00:21:39 - thought, let's start on this side, we're going to go with VLAN
00:21:43 - 115 because that's what they said, and they said VLAN 115 it's
00:21:47 - going to be this subnet, so that subnet needs to route, needs
00:21:50 - to communicate, with well, again let's rectify this, this is
00:21:54 - VLAN 8 13, over on the branch side, and on this subnet, I gotta
00:22:00 - turn word wrap on, where is word wrap, nah, it's
00:22:04 - not important. Oh but it bothers me,
00:22:09 - isn't there a quick key for that? Then maybe I just, oh, there
00:22:11 - it is, I just had to find it. So we've got the branch office
00:22:18 - 8 13, so, we'll just say branch is good, branch is good to go;
00:22:22 - although, we do will want to make sure that subnet is being routed,
00:22:25 - so you know what, before we leave the branch, I want to make
00:22:28 - sure EIGRP is advertising that subnet to the other side because
00:22:31 - that would totally be a scandalous thing to do, and would cause
00:22:35 - everything to be unreachable, so let me get, let me get over
00:22:39 - here. So BRO1, he's advertising that subnet, let's do a show
00:22:42 - run interface FA0/0.show 29,
00:22:46 - oops, 29,
00:22:49 - alright there's the subnet, so let's do show run section EIGRP,
00:22:54 - alright and that's going to take a moment so, while we're doing
00:22:58 - that, I'm also going to flip over to, see I brought over a connection
00:23:04 - to ASW1, so where is he? ASW1, yeah I got it, so meanwhile, we've
00:23:11 - got, let's see passive interface, no passive interface, in that
00:23:15 - case that's fine, we can keep the interface passive because we
00:23:18 - don't need, we're not needing to send EIGRP advertisements out
00:23:23 - that interface we just need to make sure that subnet, this subnet,
00:23:26 - right here is being advertised to the rest of the network so
00:23:28 - people know about it, so let's look, do we have a .126 in our
00:23:33 - list, no, I'm glad we checked, now let's go into router EIGRP
00:23:38 - 1, EIGRP 1, and
00:23:44 - we'll do a network 10.164.26,
00:23:49 - 0.0.0.0, specifically that interface, so now we are including
00:23:55 - this subnet in the route advertisements to the rest of the world,
00:23:59 - which is good, I'm gonna just do a show, well, yeah, I know EIGRP
00:24:04 - is doing neighbors from the last exercise, show EIGRP neighbors
00:24:08 - make sure I got neighbors with the other guys, and we do, so
00:24:11 - we're seeing our relationships form with our 2 CROs routers on
00:24:14 - the other side, so let's do this, what I'm gonna do, I'm going
00:24:19 - to say the branch is done, you're good with that? We got branch
00:24:21 - advertising that subnet, should be, let's, you know what, hey,
00:24:25 - before we do that, let's go
00:24:30 - the CROs, and let's do a show IP route, let's make sure we see
00:24:34 - that subnet showing up.
00:24:37 - Alright, we got load balancing heaven here, not concerned with
00:24:42 - all those, ok, here we go, we've got some serial links, so
00:24:48 - why am I doing this?, let's do show IP route, let's type in a
00:24:52 - specific IP address 10.1.160.,
00:24:56 - let's do, what was it, 64, the subnet, so ok, so it's that, we
00:25:02 - are learning it, via, it looks like neighbor on the frame relay
00:25:08 - 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
00:25:15 - closest to the client, so I just want to make sure that VLAN
00:25:17 - 115 exists, you know because again, from the lab they said somebody
00:25:22 - started the config, but didn't finish, so let's do a show VLAN
00:25:26 - and make sure we've got VLAN 115, so good, we've got VLAN 115,
00:25:31 - let's put our client into it, so client 1, let's do a show interface
00:25:38 - description and we've got link to client 1 FA0/8, so let's go
00:25:46 - interface FA0/8,
00:25:48 - switchboard access VLAN 115 you are moved, so we've got, now
00:25:53 - do a show VLAN
00:25:55 - make sure it looks kosher,
00:25:59 - 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
00:26:06 - got him on VLAN 115, so meanwhile, you know, I'm starting from
00:26:10 - the edge out so let's go over to client 1,
00:26:16 - where is he? That's
00:26:19 - this guy when I open the remote desktop session I just open the
00:26:23 - command prompt and say you are client 1 because I want to remember
00:26:26 - 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
00:26:33 - know, I know they don't have a DHCP scope, I don't know that,
00:26:37 - so I'm gonna do an ipconfig renew, I was going to say I know
00:26:41 - they don't have one for VLAN 115 because they didn't on the other
00:26:43 - side, so the chances are we're not going to get an address, yeah,
00:26:47 - I'm not going to wait, I know they don't have a DHCP scope configured,
00:26:51 - so let's statically configure this guy.
00:26:55 - Alright, going into our lab, acquiring network address, let's
00:27:02 - just break out of that, because sometimes it takes forever to
00:27:05 - do anything, so we're gonna go to TCP/IP and subnet on this side,
00:27:12 - again we were, here let me bring it up, it said the VLAN 115
00:27:17 - subnet would be 155.0
00:27:20 - /24. Ok, so we're gonna do, let's just, I'm going to pick a random
00:27:26 - 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
00:27:35 - hundred and his subnet mask will be this, so we got those guys
00:27:38 - documented, so that way I'll be able to test pings between them.
00:27:42 - So we've got 10.1.155.100,
00:27:48 - 255.255.255.0, 10.1.55., are you good with?, let's do
00:27:57 - 254, and the only reason I'm doing that is because the other
00:28:02 - side was 126, it was the last IP address from that subnet, so
00:28:06 - 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
00:28:12 - 254 we can come back and change it, so
00:28:17 - ok good, so we click ok
00:28:20 - on that,
00:28:23 - and so, he's good, ipconfig,
00:28:27 - got the IP address,
00:28:29 - I'm just curious. Let's do that ping 10.1.155.254,
00:28:34 - 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
00:28:39 - move back to ASW1 because again one of my project plans was not
00:28:44 - only to move, I'll just put complete on this guy, I've move client
00:28:48 - 1 to CCTV VLAN, I'm gonna verify his trunk configuration, so
00:28:52 - let's do a show interface trunk, let me make sure VLAN 115 has
00:28:57 - been added to the right guys, so it looks like we are on port
00:29:01 - channel 1, we've got 115 that has been added. So let's look here,
00:29:04 - port channel 1,
00:29:07 - which one is that, let's do a, let's do a show route, let's just
00:29:13 - check the running
00:29:15 - config, so we've got out VLANs, we've got port channel 1, so
00:29:20 - this the one to CSW1, it's got 115,
00:29:25 - is that a port channel?
00:29:27 - I guess it is, ok, so fast Ethernet 0/1 and 0/2 are going up
00:29:32 - there, which is cool, that's cool, I just only had one line,
00:29:36 - so I've must have missed the second link when I drew that diagram,
00:29:39 - then that's fine, so we've got PO1, which VLAN 115,
00:29:44 - checked, we're verified. On ASW1, is that on the port channel?
00:29:49 - so my guess is again, this is a test, I'm not going to do HSRP,
00:29:53 - I'm not going to add in both sides and route the interface and
00:29:56 - all that, I want to, I want to make client 3 ping client 1 on
00:30:01 - those two different subnets, and that's the end of the story,
00:30:03 - so I'm not going to go above and beyond on this config, if they
00:30:06 - only added it to this port channel, I'm going to follow their
00:30:09 - lead, and we're going to the get the ping going this route to
00:30:13 - CRO1, you're good with that? Alright, so let's go to, let me
00:30:20 - find them, CSW1, so let's go to the core switch and do the same
00:30:24 - thing; show the VLANs and just make sure that we've got VLAN
00:30:26 - 115. Now we're going to have to go above and beyond on this guy,
00:30:31 - ok CCTV, so we've got the VLAN, right there, let's check his
00:30:35 - trunk, let's do a show,
00:30:37 - show interface trunk, let's make sure that 115 is indeed added,
00:30:43 - it is, to port channel 1, it's not pruned, so I would say, you
00:30:47 - know at this point let me go back to my project plan, I'm gonna
00:30:49 - say this guy is complete
00:30:52 - because CSW2 is no longer in the picture; I don't care about
00:30:56 - 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
00:31:07 - VLAN 115,
00:31:11 - ok, nice, pick the random IP address, I'm guessing when they
00:31:15 - set this up, that we're gonna have this setup for HSRP or something
00:31:18 - so maybe core switch 1 would be 252, core switch 2 would be 253,
00:31:23 - and then the HSRP shared address would be .254, but again, that
00:31:29 - you know what, I'm going to verify, I'm gonna bring up the documentation,
00:31:32 - I want to make sure I didn't miss anything on the exercise instruction,
00:31:35 - they did not want us to setup, ok. Company is interested, blah,
00:31:38 - blah, blah, headquarters, branch, to keep the traffic separated
00:31:42 - CCTV solution, ok so, tomorrow, they just said, two new VLANs,
00:31:46 - one the vendor will come in and install the system. Ensure your
00:31:49 - VLANs have been created and there's an IP connectivity between
00:31:52 - 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
00:31:59 - implemented VLANs while handling other tasks but did not have
00:32:02 - time to test. You were asked to verify, so your task is to verify
00:32:07 - and ensure there's IP connectivity between the two VLANs,
00:32:11 - right, you're not, are you reading the same thing I'm reading?
00:32:13 - like there is nothing telling us to setup HSRP, it just says
00:32:19 - make them reachable, so that's what I'm gonna do, let me go over
00:32:22 - here to,
00:32:25 - I'm gonna go back to our client guy, let's see where he is, client
00:32:30 - 3, and change his default gateway to 252
00:32:36 - because that will let us get to core switch 1 as our default;
00:32:40 - we can then test the ping, and man, we can even go further, we
00:32:44 - can test end to end connectivity and see if we're there because
00:32:48 - if that's all there is to it, then great, so
00:32:51 - 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,
00:33:02 - client, here's my Excel spreadsheet, client,
00:33:07 - VLAN 115, branch office, so ok, so client
00:33:12 - 3 in the branch office is this IP address, copy, that's completed
00:33:17 - back over here, paste,
00:33:20 - I'm pinging, hey, I'm not gonna argue with that right?, so let's
00:33:25 - do a traceroute -d and paste it into there as well,
00:33:32 - I wanna make sure, dash d, if you haven't done it before, doesn't
00:33:35 - resolve the hostname, otherwise it takes like 30 seconds for
00:33:37 - every hop, it's painful, so we're going to 252, this guy is shooting
00:33:41 - us to .6, which I'm assuming is one of the CROs, one of the CRO
00:33:45 - routers, CRO router 1 shoots it to CRO router 2 or I'm not too
00:33:49 - sure why we're jumping a couple times, but we're getting right
00:33:52 - here, that's our branch office, this router here, and then our
00:33:57 - branch office router gets it to the host, so I would say, and
00:34:02 - I hope you're with me, we've moved the two hopes that both of
00:34:05 - those guys are tested and approved, we are now pinging fully
00:34:09 - between client 1 and client 3.
00:34:12 - Alright, let's do a little debrief, I have to admit I was anxious
00:34:15 - to see the solution, so I hope in the solution, I was like, is
00:34:18 - that right? Did I get it? I was like, and as soon as I saw the
00:34:20 - solution I went like: "ahhh! Are you kidding me? So I looked
00:34:24 - at the troubleshooting ticket, so first off, you might remember
00:34:26 - from the last one, I told you I reversed the scenarios because
00:34:30 - the server room fire is obviously, has to be fixed, so this trouble
00:34:34 - ticket was listed before the server room fire, so there's saying
00:34:37 - hey by the way nothing will work until you fix the server room
00:34:40 - fire, which they call trouble ticket I, I call it trouble scenario
00:34:45 - 1, so once you've fixed the server room from fire, then all you
00:34:49 - have to do to get this scenario working is change the IP address,
00:34:52 - on the fast Ethernet 0/0.29
00:34:56 - sub-interface on BRO1, and I looked at that, and I was like what
00:35:02 - oh!, let come back here to our scenario, see that, I know it's
00:35:08 - kind of goofed up right now, but originally when we came in here,
00:35:11 - I documented the IP address of BRO1 as 164.126,
00:35:18 - and so what I did is I said: "ok of that's the subnet
00:35:22 - then let's make the client be a part of that subnet" I gave him
00:35:26 - the .70 address, you remember all this, that's where I came up
00:35:28 - with this, but I failed to look at the instructions where it
00:35:31 - says, you know the branch office VLAN, and it should be .163.64,
00:35:37 - I should be using this subnet, so if you take a look, it was
00:35:40 - configured as .164, and they're saying that subnet should have
00:35:43 - been .1.163,
00:35:45 - as the subnet, now, they didn't mention anything in the solution
00:35:48 - about this VLAN 8 13, so, my guess it's just a nil error, they
00:35:52 - didn't use the right VLAN number. They didn't use 29 as the VLAN,
00:35:57 - so, so in my mind that cancels that out then, so here's what
00:36:03 - would have happened, let me just show you this, jump over to,
00:36:07 - bring up my
00:36:10 - correct router, jump over to BRO1, as soon as I saw this switch
00:36:14 - I was like ah! you're kidding me, and then I looked, and if you
00:36:16 - look under EIGRP they had a network statement of .160.0
00:36:21 - with this funky wild card mask, which would actually be the range,
00:36:25 - you know, 10.1.1.60 through 163 on that third one, so if I would
00:36:29 - have changed the subnet right here to .163
00:36:33 - from .164 then I would not have had to add this network statement
00:36:37 - to advertise this subnet, it would have just automatically be
00:36:39 - advertised because that one was in there to advertise it, but
00:36:44 - I threw my hands in the air, and I said: "we got a working solution,"
00:36:47 - we got the wrong subnet number, but I would say yes, if that
00:36:51 - were an exam environment, oops! Clicked the wrong button, I would
00:36:55 - have left a comment about that VLAN 29, VLAN.8 13, but yeah,
00:37:01 - 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
00:37:08 - have been .163; and you configured it for .164," so
00:37:12 - what else can I say? We solved scenario 2, one way or the other.
00:37:17 - For now, I hope this has been informative for you, and I'd like
00:37:20 - 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

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

comments powered by Disqus
Community Standards

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

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

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

Course Features

Speed Control

Play videos at a faster or slower pace.

Bookmarks

Pick up where you left off watching a video.

Notes

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

Closed Captions

Follow what the trainers are saying with ease.

MP3 Downloads

Listen to videos anytime, anywhere

Annual Course Features

Transcender Practice Exams

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

Jeremy Cioara

CBT Nuggets Trainer

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

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

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

Route TSHOOT: L3 Connectivity and EIGRP, Part 2
Bookmark Title:
Whoops

Login is required to access this feature.

Your browser cannot access Virtual Labs
Video Options

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

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

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