WEBVTT

0:00:09.400000 --> 0:00:15.360000
 Hello and welcome to this course from
 INE called CCNA 200-301 Practice

0:00:15.360000 --> 0:00:20.360000
 Labs. My name is Keith Bogart and I
 am the one who authored these labs

0:00:20.360000 --> 0:00:23.560000
 and will be providing these solutions
 for each of these labs as you go

0:00:23.560000 --> 0:00:27.000000
 through it. If you have any questions
 as you progress through the labs,

0:00:27.000000 --> 0:00:31.320000
 during or after the course, I have provided
 my contact information right

0:00:31.320000 --> 0:00:36.780000
 here so you can reach out to me
 in any one of these three ways.

0:00:36.780000 --> 0:00:39.700000
 So as far as these labs are concerned,
 what are the prerequisites?

0:00:39.700000 --> 0:00:43.160000
 Well, you probably will have noticed
 as far as our CCNA learning path

0:00:43.160000 --> 0:00:46.540000
 is concerned, that this course has
 been placed near the end of it.

0:00:46.540000 --> 0:00:49.920000
 And there's a reason for that is because
 these labs are really meant to

0:00:49.920000 --> 0:00:54.080000
 be done after you've progressed through
 our CCNA videos and now you're

0:00:54.080000 --> 0:00:57.360000
 ready to sort of test what you've
 learned by doing these labs.

0:00:57.360000 --> 0:01:01.960000
 Now certainly that does not mean that
 you can't do the labs at any point

0:01:01.960000 --> 0:01:05.600000
 in time that you wish as you're watching
 the videos, but at a very absolute

0:01:05.600000 --> 0:01:10.280000
 minimum, you do need to have some
 experience with the Cisco iOS CLI.

0:01:10.280000 --> 0:01:13.820000
 Now the very first lab is testing, do
 you know, the basics of the command

0:01:13.820000 --> 0:01:17.420000
 line like setting a hostname, you know,
 turning off domain name resolution,

0:01:17.420000 --> 0:01:18.860000
 things like that.

0:01:18.860000 --> 0:01:22.820000
 But after that, pretty much all the
 other labs are assuming you already

0:01:22.820000 --> 0:01:26.060000
 have some iOS command line knowledge,
 at least the basics to move around

0:01:26.060000 --> 0:01:29.960000
 to go from interface configuration back
 to global configuration to save

0:01:29.960000 --> 0:01:32.960000
 your configuration, basic
 things like that.

0:01:32.960000 --> 0:01:36.920000
 So it's also assumed you have an understanding
 of Cisco CCNA features

0:01:36.920000 --> 0:01:39.820000
 and protocols, because after all these
 labs are sort of testing you to

0:01:39.820000 --> 0:01:42.680000
 see what you've learned
 in that regard.

0:01:42.680000 --> 0:01:46.600000
 So that being the case, what's
 the objective of this?

0:01:46.600000 --> 0:01:52.060000
 Well, while there are a lot of lab tasks
 sort of sprinkled among the courses

0:01:52.060000 --> 0:01:56.980000
 in our CCNA learning path, I want to
 provide you with one course, one

0:01:56.980000 --> 0:02:00.420000
 place you could go in that learning
 path that would have a whole bunch

0:02:00.420000 --> 0:02:03.000000
 of labs right in that one course
 that you could access.

0:02:03.000000 --> 0:02:04.680000
 So that's what really
 what this is.

0:02:04.680000 --> 0:02:07.580000
 This course is not about
 teaching you concepts.

0:02:07.580000 --> 0:02:10.920000
 I'm not going to teach you OSPF or
 access lists or anything like that.

0:02:10.920000 --> 0:02:15.760000
 This is simply a course made up of nothing
 but labs, labs for you to practice

0:02:15.760000 --> 0:02:19.700000
 the things that you've learned as you've
 progressed through the CCNA.

0:02:19.700000 --> 0:02:22.920000
 And each lab also has a corresponding
 solution, which I'll talk about

0:02:22.920000 --> 0:02:24.360000
 in just one second.

0:02:24.360000 --> 0:02:27.080000
 So it's really just to give you
 some hands-on lab practice.

0:02:27.080000 --> 0:02:30.680000
 I've also given you some troubleshooting
 labs as well, because during

0:02:30.680000 --> 0:02:35.020000
 the course of taking the CCNA certification
 exam, if that is your objective,

0:02:35.020000 --> 0:02:38.240000
 you might be given something like a multiple
 choice question that provides

0:02:38.240000 --> 0:02:41.420000
 you some output of a router
 or output of a switch.

0:02:41.420000 --> 0:02:43.680000
 And the question might
 describe a problem.

0:02:43.680000 --> 0:02:47.460000
 And then based on what the problem
 is and the output that you see, you

0:02:47.460000 --> 0:02:51.060000
 might have to select from among the
 answers what the issue is or what

0:02:51.060000 --> 0:02:53.780000
 command you'd have to type
 to fix that problem.

0:02:53.780000 --> 0:02:57.320000
 So I thought, what better way to prepare
 you for something like that than

0:02:57.320000 --> 0:03:01.060000
 to give you some actual troubleshooting
 labs where you're presented with

0:03:01.060000 --> 0:03:04.420000
 a problem. And as soon as you start
 up the lab, that problem is already

0:03:04.420000 --> 0:03:08.000000
 there. There's already something that
 you have to actually go in, find

0:03:08.000000 --> 0:03:11.120000
 what the problem is,
 and fix the problem.

0:03:11.120000 --> 0:03:14.520000
 Much more satisfying than just answering
 a multiple choice question about

0:03:14.520000 --> 0:03:19.240000
 something. So let me talk a little bit
 about the lab guidelines to help

0:03:19.240000 --> 0:03:24.000000
 make it as efficient and enjoyable as
 possible for you while you go through

0:03:24.000000 --> 0:03:27.760000
 the lab. So let's start up with what
 you can expect when you start up

0:03:27.760000 --> 0:03:32.060000
 the labs. Now, at the time that I'm
 recording this video right now, this

0:03:32.060000 --> 0:03:34.120000
 course is not actually
 on our platform.

0:03:34.120000 --> 0:03:37.620000
 So I'm going to have to sort of demonstrate
 this using other courses.

0:03:37.620000 --> 0:03:43.380000
 So when you get to any particular lab,
 this is the one of the labs in

0:03:43.380000 --> 0:03:45.900000
 the course, but this is an example
 of what it will look like.

0:03:45.900000 --> 0:03:50.060000
 You'll see some sort of a topology
 diagram, maybe one or two lines of

0:03:50.060000 --> 0:03:54.480000
 like an intro or maybe some things to
 be concerned with, then you'll have

0:03:54.480000 --> 0:03:59.380000
 tasks. Now, when you click on tasks,
 that's where you actually read, this

0:03:59.380000 --> 0:04:00.460000
 is what you're supposed to do.

0:04:00.460000 --> 0:04:04.560000
 So even before you start the lab, before
 you click the start lab button,

0:04:04.560000 --> 0:04:09.540000
 you should run through the tasks as you
 see them on here, familiar familiarize

0:04:09.540000 --> 0:04:13.700000
 yourself with what is being asked
 of you in this particular lab.

0:04:13.700000 --> 0:04:16.860000
 Okay, when you're ready to work through
 the tasks, you'll go ahead and

0:04:16.860000 --> 0:04:18.680000
 click on start lab.

0:04:18.680000 --> 0:04:21.840000
 Now, when you click on the start lab
 button, you'll get an experience

0:04:21.840000 --> 0:04:28.460000
 like this. You'll start
 out black like this.

0:04:28.460000 --> 0:04:33.200000
 And then if everything works correctly,
 you should gain access to an Ubuntu

0:04:33.200000 --> 0:04:35.960000
 virtual machine.

0:04:35.960000 --> 0:04:38.860000
 And that Ubuntu virtual machine is actually
 running the lab environment

0:04:38.860000 --> 0:04:41.380000
 in it. So just wait,
 just be patient.

0:04:41.380000 --> 0:04:44.800000
 And in just a couple of seconds, the
 lab environment should come up.

0:04:44.800000 --> 0:04:47.140000
 There it is. So it's it's
 automatically connecting.

0:04:47.140000 --> 0:04:50.240000
 And you'll notice the moment you see
 the topology that every single device

0:04:50.240000 --> 0:04:52.320000
 has little red circles around it.

0:04:52.320000 --> 0:04:55.120000
 That means those devices
 are powered off.

0:04:55.120000 --> 0:04:58.700000
 But if you just wait and don't touch
 anything, like right now, now is

0:04:58.700000 --> 0:05:01.280000
 how those red squares
 turn to green.

0:05:01.280000 --> 0:05:05.560000
 So just wait a few seconds and all the
 devices will power on automatically.

0:05:05.560000 --> 0:05:08.840000
 Now, here's where I recommend that you
 do the moment a device powers on

0:05:08.840000 --> 0:05:12.700000
 just pick one doesn't matter anyone like
 I'll pick router one here, right

0:05:12.700000 --> 0:05:17.380000
 click on it and select console and
 make sure the little console window

0:05:17.380000 --> 0:05:19.480000
 pops up. Give it a couple seconds.


0:05:19.480000 --> 0:05:20.780000
 All right, there it is.

0:05:20.780000 --> 0:05:22.780000
 All right, so that's good.

0:05:22.780000 --> 0:05:25.800000
 Now, sometimes when you start a
 lab, that's not going to happen.

0:05:25.800000 --> 0:05:28.840000
 You're going to right click on a device,
 select console and just no console

0:05:28.840000 --> 0:05:29.940000
 window will start up.

0:05:29.940000 --> 0:05:33.280000
 I don't honestly know why that is, but
 I will show you what the solution

0:05:33.280000 --> 0:05:37.040000
 to it is. And I've also written the
 solution into the beginning of every

0:05:37.040000 --> 0:05:40.060000
 single lab in case you forget
 what I'm showing you here.

0:05:40.060000 --> 0:05:45.220000
 So let's say that you right click on
 a lab on a device, we're not able

0:05:45.220000 --> 0:05:46.220000
 to get the console.

0:05:46.220000 --> 0:05:51.400000
 Here's what you do in the lower
 left corner down here.

0:05:51.400000 --> 0:05:54.840000
 There is a little icon
 for Q terminal.

0:05:54.840000 --> 0:06:02.860000
 So this will open up the terminal app
 and just type in a single command

0:06:02.860000 --> 0:06:08.360000
 reboot. And this will reboot the virtual
 machine that's running your lab.

0:06:08.360000 --> 0:06:10.040000
 It'll say you've been
 disconnected.

0:06:10.040000 --> 0:06:13.220000
 So just wait around
 15 or 20 seconds.

0:06:13.220000 --> 0:06:14.820000
 You don't have to wait very long.

0:06:14.820000 --> 0:06:20.060000
 And then after 15 or 20 seconds, click
 on the reconnect button and you

0:06:20.060000 --> 0:06:21.840000
 should be able to reconnect
 back into the lab.

0:06:21.840000 --> 0:06:25.320000
 And now, when you right click on a
 device, you should be able to get a

0:06:25.320000 --> 0:06:30.920000
 console window. So that's
 what you start a lab.

0:06:30.920000 --> 0:06:34.540000
 Or if during a lab, for some weird reason,
 all of a sudden you can't get

0:06:34.540000 --> 0:06:36.000000
 into a device that
 shouldn't happen.

0:06:36.000000 --> 0:06:39.480000
 But if it does, this is the
 fix all for all of that.

0:06:39.480000 --> 0:06:44.240000
 All right, the next thing I want to
 show you is when you start up a lab,

0:06:44.240000 --> 0:06:50.980000
 if you do this, view, click on view,
 docs and server summary, all right,

0:06:50.980000 --> 0:06:52.600000
 and just pull this
 out a little bit.

0:06:52.600000 --> 0:07:02.080000
 Notice right now that the so if I tried
 to get into one of these devices

0:07:02.080000 --> 0:07:06.220000
 right now and I got the console and I
 tried typing things, there's a good

0:07:06.220000 --> 0:07:08.940000
 chance that my devices would
 be very, very slow.

0:07:08.940000 --> 0:07:13.220000
 I might get some memory issues, because
 it's making the console work pretty

0:07:13.220000 --> 0:07:17.560000
 hard to boot up all these devices
 all at the same time.

0:07:17.560000 --> 0:07:20.620000
 But if you wait just two or three minutes,
 like look at this, in the time

0:07:20.620000 --> 0:07:24.060000
 I started this lab, which has only
 been a couple of minutes, now it's

0:07:24.060000 --> 0:07:28.380000
 dropping down to 60%, 50%,
 something like that.

0:07:28.380000 --> 0:07:32.840000
 So the moral of that story is once you
 start a lab, step number one, right

0:07:32.840000 --> 0:07:37.260000
 click on a device as soon as possible
 after it turns green and make sure

0:07:37.260000 --> 0:07:38.540000
 you can get the console.

0:07:38.540000 --> 0:07:42.500000
 If you can't reboot the virtual machine
 using that method I told you about.

0:07:42.500000 --> 0:07:46.640000
 Number two, if you are able to reboot
 the console, just sit back and wait

0:07:46.640000 --> 0:07:47.700000
 like two minutes.

0:07:47.700000 --> 0:07:51.400000
 And that should be all it takes
 for the CPU to calm down here.

0:07:51.400000 --> 0:07:57.620000
 And like I said, if you want to see the
 CPU, it's just view, docs, server

0:07:57.620000 --> 0:08:00.480000
 summary. Now once you've confirmed that
 this has dropped down to something

0:08:00.480000 --> 0:08:04.500000
 like 60% or less, you can just close
 it, click on the little X here, we

0:08:04.500000 --> 0:08:07.880000
 don't need to see that anymore, and
 you can start working on your lab.

0:08:07.880000 --> 0:08:12.840000
 Now, let me go back to what
 we were looking at before.

0:08:12.840000 --> 0:08:15.800000
 So reusing lab topologies.

0:08:15.800000 --> 0:08:20.060000
 When you start up a lab, these labs do
 have a hard and fast timer of about

0:08:20.060000 --> 0:08:22.880000
 an hour, I think it's
 like 55 minutes.

0:08:22.880000 --> 0:08:27.220000
 So the lab will automatically shut
 off and kick you out after an hour.

0:08:27.220000 --> 0:08:31.760000
 But an hour should be more than enough
 time for you to accomplish whatever

0:08:31.760000 --> 0:08:33.960000
 you need to accomplish in any
 of these practice labs.

0:08:33.960000 --> 0:08:36.060000
 But just be aware of that, that's
 the hard and fast timer.

0:08:36.060000 --> 0:08:39.740000
 So if you get up and walk away to eat
 something or take a break, chances

0:08:39.740000 --> 0:08:43.420000
 are by the time you come back, the
 lab will have turned itself off.

0:08:43.420000 --> 0:08:48.440000
 Now, let's say that I do lab number
 one in about 15 minutes.

0:08:48.440000 --> 0:08:52.680000
 And I think, you know what, rather than
 just stopping this and starting

0:08:52.680000 --> 0:08:57.280000
 up lab number two, I just keep this
 running and open up lab number two,

0:08:57.280000 --> 0:09:01.200000
 you know, like like this, let's say
 this was lab number two, let me look

0:09:01.200000 --> 0:09:04.040000
 at the directions here and I'll just
 use these directions on the current

0:09:04.040000 --> 0:09:06.860000
 lab, I just finished
 with lab number one.

0:09:06.860000 --> 0:09:09.680000
 Why do I have to keep stopping
 and restarting topologies?

0:09:09.680000 --> 0:09:12.800000
 Well, you actually should stop
 and restart the topologies.

0:09:12.800000 --> 0:09:18.260000
 And here's the lab's when you click
 the start lab button, the topology

0:09:18.260000 --> 0:09:22.100000
 will come up with some kind of
 a pre configuration in it.

0:09:22.100000 --> 0:09:26.460000
 So if I use the same topology, and let's
 say I was able to bang out four

0:09:26.460000 --> 0:09:31.040000
 labs in the one hour that I have, that's
 not a good thing, because now

0:09:31.040000 --> 0:09:35.360000
 you're neglecting the pre configurations
 that came with lab two, lab three,

0:09:35.360000 --> 0:09:41.180000
 lab four. So it's just a better idea
 to stop a lab when you're done, which

0:09:41.180000 --> 0:09:45.500000
 completely tears down the virtual machine,
 go on to the next lab, click

0:09:45.500000 --> 0:09:49.500000
 the start lab button for the next lab,
 which starts up a whole other virtual

0:09:49.500000 --> 0:09:52.420000
 machine with a pre configuration
 loaded in it.

0:09:52.420000 --> 0:09:58.240000
 So don't use the same lab environment
 for multiple lab tasks, just not

0:09:58.240000 --> 0:10:04.260000
 a good idea, not to mention you only
 have a one hour limit anyway.

0:10:04.260000 --> 0:10:06.540000
 All right, lab order.

0:10:06.540000 --> 0:10:11.280000
 So you don't really have to do the
 labs in any particular order.

0:10:11.280000 --> 0:10:15.500000
 I would recommend that you start with
 lab number one, which is like the

0:10:15.500000 --> 0:10:19.480000
 iOS basics lab. And I think there's
 some IP before addressing in there.

0:10:19.480000 --> 0:10:21.960000
 So I would recommend
 you start with that.

0:10:21.960000 --> 0:10:28.800000
 Then, so of the 25 labs I've created for
 this course, 15 of them are configuration

0:10:28.800000 --> 0:10:32.840000
 labs, where you're asked to configure
 various features and protocols and

0:10:32.840000 --> 0:10:37.140000
 things. So of those first 15 labs,
 I do recommend that you start with

0:10:37.140000 --> 0:10:41.720000
 lab number one. Now, of the remaining
 14 labs after that, you can do them

0:10:41.720000 --> 0:10:43.500000
 in any order that you wish.

0:10:43.500000 --> 0:10:46.040000
 One lab is not dependent
 upon another.

0:10:46.040000 --> 0:10:49.760000
 So just start with lab number one and
 ideally you'd progress through them

0:10:49.760000 --> 0:10:51.540000
 in order, but you don't have to.

0:10:51.540000 --> 0:10:54.900000
 Now, as far as the troubleshooting labs are
 concerned, there's 10 troubleshooting

0:10:54.900000 --> 0:10:58.540000
 labs. Those ones, you really
 should progress in order.

0:10:58.540000 --> 0:11:01.940000
 They do get progressively more
 difficult as you go on.

0:11:01.940000 --> 0:11:05.820000
 So I would recommend
 that solutions.

0:11:05.820000 --> 0:11:07.100000
 Okay, so let's talk
 about solutions.

0:11:07.100000 --> 0:11:09.040000
 So for that, I'm going
 to go back to this.

0:11:09.040000 --> 0:11:13.800000
 Now, most of now this is somebody else's
 course, another instructor here

0:11:13.800000 --> 0:11:16.260000
 at INE by just using
 this as an example.

0:11:16.260000 --> 0:11:20.720000
 So the every single lab that I've created
 for this course, when you click

0:11:20.720000 --> 0:11:25.160000
 on solutions, you'll see this, you'll see
 some verbiage about see a corresponding

0:11:25.160000 --> 0:11:30.080000
 video. And over here on the right is
 a button or a link that says reveal

0:11:30.080000 --> 0:11:35.160000
 solution. And if you click on that
 link, it will open up a video of me

0:11:35.160000 --> 0:11:38.340000
 doing a walkthrough of the
 solution for that lab.

0:11:38.340000 --> 0:11:42.220000
 So if you got stuck during the lab and
 weren't able to finish it, or maybe

0:11:42.220000 --> 0:11:45.000000
 you did finish it and you're wondering,
 Hmm, I wonder if I did it the

0:11:45.000000 --> 0:11:48.840000
 right and correct way, you can click
 on that reveal solution, open up

0:11:48.840000 --> 0:11:52.260000
 a video, and I will show you how I
 complete the lab from beginning to

0:11:52.260000 --> 0:11:58.860000
 end. So as far as the troubleshooting labs
 are concerned, the troubleshooting

0:11:58.860000 --> 0:12:02.100000
 labs will also have a walk
 through video solution.

0:12:02.100000 --> 0:12:05.580000
 But in addition to that, when you click
 on the solutions button, there

0:12:05.580000 --> 0:12:10.920000
 will be a little bit of verbiage in
 here saying at a high level, what

0:12:10.920000 --> 0:12:12.800000
 the troubleshooting problem was.

0:12:12.800000 --> 0:12:16.060000
 It might say something like in this
 lab, the problem that you had to fix

0:12:16.060000 --> 0:12:19.280000
 was that router one had
 incorrect IP addressing.

0:12:19.280000 --> 0:12:22.580000
 So for example, let's say that you completed
 troubleshooting lab number

0:12:22.580000 --> 0:12:25.620000
 one, you discovered, Oh, I
 think this is the problem.

0:12:25.620000 --> 0:12:28.120000
 I found some incorrect IP
 addressing on router one.

0:12:28.120000 --> 0:12:30.900000
 You fix that, you're able
 to ping or something.

0:12:30.900000 --> 0:12:34.720000
 Now you click on solution and low and
 behold, it says in the text, router

0:12:34.720000 --> 0:12:36.660000
 one had some wrong IP addressing.

0:12:36.660000 --> 0:12:39.940000
 Then that's it. You don't really
 need to watch the solution video.

0:12:39.940000 --> 0:12:44.340000
 But if you are on troubleshooting video,
 let's say number six, and either

0:12:44.340000 --> 0:12:49.620000
 you got completely stuck, or you did
 fix something and you were able to

0:12:49.620000 --> 0:12:52.660000
 get your pings to work, but you're
 wondering, I wonder if what I found

0:12:52.660000 --> 0:12:57.760000
 and what I fixed is really what the
 author intended for me to find and

0:12:57.760000 --> 0:13:01.480000
 fix. Well, then you can read through
 this, you know, what that little

0:13:01.480000 --> 0:13:06.080000
 brief paragraph of a blurb is, and maybe
 you'll discover, Oh, that paragraph

0:13:06.080000 --> 0:13:10.480000
 is this guy describing something
 that that's not what I did.

0:13:10.480000 --> 0:13:13.460000
 So then you can click on
 the reveal solution link.

0:13:13.460000 --> 0:13:17.280000
 And like the other labs, you'll see
 me do a walkthrough solution of how

0:13:17.280000 --> 0:13:20.260000
 to troubleshoot that particular
 environment.

0:13:20.260000 --> 0:13:22.920000
 So the troubleshooting videos
 will be like this.

0:13:22.920000 --> 0:13:27.140000
 Basically no solution, but a reveal
 solution link with maybe a little

0:13:27.140000 --> 0:13:31.340000
 bit of text right here, the configuration
 videos, there's no text at all

0:13:31.340000 --> 0:13:35.580000
 in the solutions section to see the
 solution you have to click on the

0:13:35.580000 --> 0:13:39.860000
 reveal solution link
 to watch the video.

0:13:39.860000 --> 0:13:42.300000
 I already mentioned how the
 labs are one hour long.

0:13:42.300000 --> 0:13:44.860000
 That's a hard and fast limit.

0:13:44.860000 --> 0:13:46.980000
 And I've covered these
 two things right here.

0:13:46.980000 --> 0:13:47.820000
 So we're good to go.

0:13:47.820000 --> 0:13:50.140000
 So that's it for my
 introduction here.

0:13:50.140000 --> 0:13:52.480000
 So at this point, you
 should be ready to go.

0:13:52.480000 --> 0:13:55.700000
 You got all the information you need
 to progress with these labs.

0:13:55.700000 --> 0:13:59.240000
 So have fun with our
 CCNA practice labs.