WEBVTT

0:00:07.960000 --> 0:00:12.280000
 In the previous video, we started
 the download process of GNS3.

0:00:12.280000 --> 0:00:16.100000
 We started the opening of the application
 for the very first time, and

0:00:16.100000 --> 0:00:19.060000
 we went through the initial steps of
 the setup wizard where all of the

0:00:19.060000 --> 0:00:24.200000
 different applications like GNS3, Dynamips,
 Wireshark, we're all downloaded

0:00:24.200000 --> 0:00:26.000000
 and installed into our laptop.

0:00:26.000000 --> 0:00:28.740000
 So now we're going to continue that
 process and see what the next steps

0:00:28.740000 --> 0:00:32.580000
 are because we're not quite ready yet
 to create our virtual topologies.

0:00:32.580000 --> 0:00:38.120000
 So next thing is we're going to hit
 the finish button, and what you're

0:00:38.120000 --> 0:00:41.500000
 not seeing is that there's
 a screen on my laptop.

0:00:41.500000 --> 0:00:44.580000
 Basically, just a web browser that will
 come up from GNS3 saying, thank

0:00:44.580000 --> 0:00:46.800000
 you for downloading our software.

0:00:46.800000 --> 0:00:49.320000
 And then this box will come up.

0:00:49.320000 --> 0:00:52.060000
 So at this point, we have
 a choice to make.

0:00:52.060000 --> 0:00:56.660000
 So we can either run GNS3 on the local
 server or within a virtual machine.

0:00:56.660000 --> 0:00:58.720000
 So let me just talk about
 that real briefly here.

0:00:58.720000 --> 0:01:04.040000
 First of all, if your primary reason
 for using GNS3 is that you just want

0:01:04.040000 --> 0:01:08.360000
 to create Cisco topologies, you want
 to practice Cisco iOS command line

0:01:08.360000 --> 0:01:12.940000
 routers, and you want to connect them
 together, then really all you have

0:01:12.940000 --> 0:01:17.120000
 to do is select the local server option,
 which is not selected by default

0:01:17.120000 --> 0:01:22.540000
 right there. And what local server
 simply means is that it means that

0:01:22.540000 --> 0:01:26.980000
 GNS3 will be running on your laptop just
 like a normal program, just like

0:01:26.980000 --> 0:01:31.460000
 Microsoft Outlook or Google Chrome or
 anything else you've got running,

0:01:31.460000 --> 0:01:33.240000
 it'll just run directly on there.

0:01:33.240000 --> 0:01:36.420000
 And quite frankly, if you're just doing
 basic Cisco topologies, that's

0:01:36.420000 --> 0:01:38.260000
 probably the preferred way to go.

0:01:38.260000 --> 0:01:43.700000
 Now if you're a more advanced user,
 then you probably want to select the

0:01:43.700000 --> 0:01:46.500000
 local GNS3 virtual machine.

0:01:46.500000 --> 0:01:49.980000
 Now this will also require that you've
 already downloaded and installed

0:01:49.980000 --> 0:01:56.480000
 either virtual box or some flavor of
 VMware, because the virtual machine

0:01:56.480000 --> 0:02:01.240000
 will use a virtual box or VMware as sort
 of like the engine that's running

0:02:01.240000 --> 0:02:05.740000
 everything. Now like I said, if you're
 just running simple Cisco topologies

0:02:05.740000 --> 0:02:09.160000
 with routers and switches, you don't
 really need to go the extra distance

0:02:09.160000 --> 0:02:10.540000
 of doing the virtual machine.

0:02:10.540000 --> 0:02:13.020000
 There's a lot of extra steps
 involved with that.

0:02:13.020000 --> 0:02:16.500000
 But if you're more an intermediate or
 advanced user and you want to start

0:02:16.500000 --> 0:02:22.500000
 doing things like okay, I want to pair
 up my virtual topology with a Cisco

0:02:22.500000 --> 0:02:29.480000
 ASA, some kind of a firewall, or maybe
 I want to use IOU or L2 IOU and

0:02:29.480000 --> 0:02:32.400000
 I want to pair that up with
 my virtual topology.

0:02:32.400000 --> 0:02:35.800000
 In those particular cases, now we have
 to start getting virtual machines

0:02:35.800000 --> 0:02:39.320000
 involved. But that's more complex stuff
 and we're not going to cover that

0:02:39.320000 --> 0:02:41.820000
 in this particular
 series of videos.

0:02:41.820000 --> 0:02:45.200000
 So to keep things simple, I'm just going
 to install it as a local server

0:02:45.200000 --> 0:02:50.480000
 directly on my laptop, no virtual
 machines necessary.

0:02:50.480000 --> 0:02:56.080000
 And now we get to the point where we
 get to choose what iOS image we want

0:02:56.080000 --> 0:02:58.660000
 to import into GNS3.

0:02:58.660000 --> 0:03:03.280000
 So we select finish and now we have
 a box that comes up that says okay,

0:03:03.280000 --> 0:03:06.360000
 now it's probably going to look like
 this for you if you've done this

0:03:06.360000 --> 0:03:07.720000
 the very first time.

0:03:07.720000 --> 0:03:10.760000
 And here's where you get to browse
 for wherever you've downloaded your

0:03:10.760000 --> 0:03:12.200000
 Cisco iOS software to.

0:03:12.200000 --> 0:03:16.120000
 So I'm going to browse
 in my particular case.

0:03:16.120000 --> 0:03:21.080000
 I've got my iOS images located in external
 hard drive called Cisco iOS

0:03:21.080000 --> 0:03:23.080000
 and there they are.

0:03:23.080000 --> 0:03:25.000000
 Now let me show you what something
 is kind of interesting.

0:03:25.000000 --> 0:03:30.400000
 And in previous videos, I talked about
 that GNS3 only supports certain

0:03:30.400000 --> 0:03:31.960000
 software images.

0:03:31.960000 --> 0:03:35.500000
 It doesn't support every single router
 out there that Cisco does.

0:03:35.500000 --> 0:03:40.340000
 Now what if you had ignored that and
 you downloaded a Cisco iOS software

0:03:40.340000 --> 0:03:42.480000
 image that GNS3 didn't support?

0:03:42.480000 --> 0:03:43.680000
 What would happen?

0:03:43.680000 --> 0:03:45.480000
 Well let's take a look at that.

0:03:45.480000 --> 0:03:51.560000
 I already know in advance that the
 3845 at present is not supported by

0:03:51.560000 --> 0:03:55.220000
 GNS3. So I'm going to go ahead
 and select that intentionally.

0:03:55.220000 --> 0:03:57.760000
 I'm going to click open.

0:03:57.760000 --> 0:04:00.960000
 Okay. And then it says alright, so
 basically it wants to move that iOS

0:04:00.960000 --> 0:04:04.460000
 into a working directory that
 GNS3 can access more quickly.

0:04:04.460000 --> 0:04:05.660000
 So I'll say yes.

0:04:05.660000 --> 0:04:08.400000
 Yes. No error messages yet.

0:04:08.400000 --> 0:04:13.620000
 Click next. And then I get the error
 message where it says the iOS image

0:04:13.620000 --> 0:04:17.320000
 for that particular platform is not
 supported by this application.

0:04:17.320000 --> 0:04:21.280000
 So even if you didn't do your research
 ahead of time, you'll get that

0:04:21.280000 --> 0:04:24.260000
 error message. Now hopefully you didn't
 spend a lot of time and money

0:04:24.260000 --> 0:04:30.180000
 downloading an iOS software image that
 ultimately you can't use in GNS3.

0:04:30.180000 --> 0:04:36.480000
 Now in my particular case, I'm going to
 use a 3745 image which I've already

0:04:36.480000 --> 0:04:38.360000
 downloaded and got here.

0:04:38.360000 --> 0:04:41.200000
 Now before I leave the screen, notice
 there's a little box here that says

0:04:41.200000 --> 0:04:43.880000
 this is an ether switch router.

0:04:43.880000 --> 0:04:48.900000
 Once we get into the world of switching
 with GNS3, we'll see that we've

0:04:48.900000 --> 0:04:51.380000
 got two sort of high
 level choices.

0:04:51.380000 --> 0:04:54.900000
 Actually we have three choices, but for
 the basic world of switching there's

0:04:54.900000 --> 0:04:59.100000
 two choices. The two choices are GNS3
 comes with sort of like a built

0:04:59.100000 --> 0:05:02.160000
 in very simple switch.

0:05:02.160000 --> 0:05:04.960000
 Like I talked about in the previous
 video, I talked about the virtual

0:05:04.960000 --> 0:05:07.520000
 PC simulator that comes built in.

0:05:07.520000 --> 0:05:09.460000
 Well, that's not a
 full fledged PC.

0:05:09.460000 --> 0:05:11.920000
 That's not running Windows
 or anything like that.

0:05:11.920000 --> 0:05:15.240000
 It's basically a real stripped down
 PC that just allows you to do like

0:05:15.240000 --> 0:05:19.360000
 TCP and UDP streams and some
 ICMP and stuff like that.

0:05:19.360000 --> 0:05:24.020000
 Well similarly, there's something called
 a built in node which is a switch

0:05:24.020000 --> 0:05:28.460000
 node. And if you select that, you can
 select VLANs on there, you can select

0:05:28.460000 --> 0:05:31.740000
 802.1Q trunking and
 that's about it.

0:05:31.740000 --> 0:05:35.920000
 So there's no command line, it's all
 GUI driven with little drop down

0:05:35.920000 --> 0:05:37.200000
 boxes and stuff.

0:05:37.200000 --> 0:05:39.760000
 So for simple switching, if you just
 want to connect some routers with

0:05:39.760000 --> 0:05:43.660000
 a switch and you don't really care about
 actually configuring switches,

0:05:43.660000 --> 0:05:45.480000
 that's your easiest option.

0:05:45.480000 --> 0:05:49.000000
 Now if you want to get a little bit
 more experience which you probably

0:05:49.000000 --> 0:05:53.340000
 will, actually configuring the command
 line for switching commands like

0:05:53.340000 --> 0:05:58.760000
 configuring a VLAN in the command line,
 configuring VTP, modifying some

0:05:58.760000 --> 0:06:01.220000
 of your spanning tree parameters.

0:06:01.220000 --> 0:06:04.380000
 Well then your next choice is to use
 something called an ether switch

0:06:04.380000 --> 0:06:09.060000
 module. I'll talk more about that in
 detail, but of all the Cisco routers

0:06:09.060000 --> 0:06:14.420000
 that GNS3 supports, some of them, like
 the 3745 that I'm going to select

0:06:14.420000 --> 0:06:18.040000
 here, support that
 particular module.

0:06:18.040000 --> 0:06:20.640000
 And it's actually a module that in
 a real router you would slip in.

0:06:20.640000 --> 0:06:25.020000
 It actually has 16 ports on it and
 it's like a little mini switch that

0:06:25.020000 --> 0:06:28.340000
 you sort of slide in to an
 empty slot in your router.

0:06:28.340000 --> 0:06:32.240000
 So in this particular case, if that's
 what I wanted, I would actually

0:06:32.240000 --> 0:06:37.560000
 click that box. So what I'm going to
 do is I'm actually going to do this

0:06:37.560000 --> 0:06:40.820000
 twice. The first time I'm just going
 to import this as a normal router

0:06:40.820000 --> 0:06:43.160000
 without that module.

0:06:43.160000 --> 0:06:45.960000
 So I'll hit next.

0:06:45.960000 --> 0:06:47.240000
 Actually, you know what?

0:06:47.240000 --> 0:06:49.460000
 Let's make it simple
 for ourselves.

0:06:49.460000 --> 0:06:53.940000
 Because even the ether switch router,
 even though it's got that module

0:06:53.940000 --> 0:06:58.240000
 in it that's the ether switch, it also
 has other module slots available

0:06:58.240000 --> 0:07:03.220000
 for like fast ethernet cars, our routable
 interfaces, serial interfaces.

0:07:03.220000 --> 0:07:07.320000
 So to make things simple, let's just
 have, well, just to show you, I'll

0:07:07.320000 --> 0:07:09.800000
 have a router and an ether switch
 to show you the variety.

0:07:09.800000 --> 0:07:13.980000
 But what I was going to say was you
 could just have every router in your

0:07:13.980000 --> 0:07:16.980000
 topology as an ether switch.

0:07:16.980000 --> 0:07:20.020000
 And you could use the switching module
 in some of them and you could not

0:07:20.020000 --> 0:07:22.000000
 use the switching module
 in others of them.

0:07:22.000000 --> 0:07:24.720000
 But all of them could have serial
 interfaces and stuff like that.

0:07:24.720000 --> 0:07:28.460000
 But to show you the difference,
 I'll just keep on going here.

0:07:28.460000 --> 0:07:33.080000
 Now what's kind of interesting here
 is in the process of creating these

0:07:33.080000 --> 0:07:37.160000
 videos, I've installed and uninstalled
 GNS3 multiple times.

0:07:37.160000 --> 0:07:40.480000
 And even though I've done that, it's
 remembering some of the stuff I've

0:07:40.480000 --> 0:07:41.600000
 done previously.

0:07:41.600000 --> 0:07:44.940000
 If you're doing this for the very first
 time, chances are it's not going

0:07:44.940000 --> 0:07:47.640000
 to default to 256
 megabytes of RAM.

0:07:47.640000 --> 0:07:52.560000
 I think it actually defaults
 to 128 megabytes of RAM.

0:07:52.560000 --> 0:07:55.800000
 So you're going to want to verify,
 like I said in some of the previous

0:07:55.800000 --> 0:08:01.420000
 videos, what the RAM requirements
 are for your software image.

0:08:01.420000 --> 0:08:06.380000
 Now my particular case with this 30,
 actually 3845, nope, that's wrong.

0:08:06.380000 --> 0:08:08.520000
 I don't want to 3845.

0:08:08.520000 --> 0:08:10.620000
 That is the wrong image.

0:08:10.620000 --> 0:08:14.400000
 So let's go ahead and use
 the existing image.

0:08:14.400000 --> 0:08:18.720000
 It remembered this even though I've installed
 and uninstalled everything.

0:08:18.720000 --> 0:08:21.280000
 3725, there we go.

0:08:21.280000 --> 0:08:22.900000
 There we go. 128 megabytes of RAM.


0:08:22.900000 --> 0:08:29.860000
 That is wrong. I need to double
 that to 256 megabytes of RAM.

0:08:29.860000 --> 0:08:31.020000
 Then click next.

0:08:31.020000 --> 0:08:35.980000
 And now here's where I get to select
 what modules or port adapters I want

0:08:35.980000 --> 0:08:41.600000
 in my chassis. And so the nice thing
 about this is, a question I had when

0:08:41.600000 --> 0:08:45.880000
 I was first learning about GNS3 was
 I wondered, well, if I fully load

0:08:45.880000 --> 0:08:50.520000
 this thing, if I populate every slot
 with something, is that going to

0:08:50.520000 --> 0:08:53.320000
 hurt things? Is that going to
 slow it down in some way?

0:08:53.320000 --> 0:08:54.920000
 And actually, it doesn't.

0:08:54.920000 --> 0:08:58.380000
 I was actually told by the GNS3 developers
 itself that you can do that.

0:08:58.380000 --> 0:09:00.020000
 There's no harm in doing that.

0:09:00.020000 --> 0:09:01.500000
 So, go right ahead.

0:09:01.500000 --> 0:09:02.980000
 So I'm going to go
 ahead and do that.

0:09:02.980000 --> 0:09:05.920000
 And it comes with a fast ethernet
 slot already on it.

0:09:05.920000 --> 0:09:09.500000
 Now this is just because of this particular
 router that I've selected.

0:09:09.500000 --> 0:09:12.340000
 And another slot I'm going to put another
 fast ethernet card, and then

0:09:12.340000 --> 0:09:14.380000
 I'll put another fast
 ethernet card.

0:09:14.380000 --> 0:09:18.180000
 And as I go forward, I've got
 some wick slots available.

0:09:18.180000 --> 0:09:22.600000
 Once again, these are slots available
 in the 3725, depending on the software

0:09:22.600000 --> 0:09:26.860000
 that you are using, you might not have
 all of these available to you.

0:09:26.860000 --> 0:09:29.360000
 Or you might have more, just
 depending on what software.

0:09:29.360000 --> 0:09:33.960000
 So I'm going to put some serial interfaces
 in these slots right here.

0:09:33.960000 --> 0:09:36.940000
 So I'm going to have tons of interfaces
 in every single one of my router

0:09:36.940000 --> 0:09:42.380000
 to give me lots of flexibility in the
 types of topologies that I design.

0:09:42.380000 --> 0:09:47.960000
 Click Next. All right, so it's
 thinking about a little bit.

0:09:47.960000 --> 0:09:49.920000
 Oops, I want to go back there.

0:09:49.920000 --> 0:10:03.160000
 So let's edit. Okay, well the thing
 that skipped past was the idle PC.

0:10:03.160000 --> 0:10:05.860000
 So I want to show that to you.

0:10:05.860000 --> 0:10:08.340000
 So I'm going to go ahead
 and remove this.

0:10:08.340000 --> 0:10:09.360000
 And here's a good
 way of doing that.

0:10:09.360000 --> 0:10:12.580000
 So once it's in there, you just
 click Delete to get rid of it.

0:10:12.580000 --> 0:10:17.400000
 And to add a new router, or an additional
 router, you just click New.

0:10:17.400000 --> 0:10:19.180000
 So let's just go through
 the process here.

0:10:19.180000 --> 0:10:21.260000
 Everything's going to be the same.


0:10:21.260000 --> 0:10:26.800000
 Upgrade my memory.

0:10:26.800000 --> 0:10:29.340000
 And this is up. Hold on a second.

0:10:29.340000 --> 0:10:37.960000
 Let's put my cards in here.

0:10:37.960000 --> 0:10:42.940000
 All right, the idle PC.

0:10:42.940000 --> 0:10:45.840000
 This definitely bears a little
 bit of discussion.

0:10:45.840000 --> 0:10:49.180000
 I'm not going to go into the gory details
 of how this works at the low

0:10:49.180000 --> 0:10:50.900000
 level mechanics and everything.

0:10:50.900000 --> 0:10:53.100000
 But here's what I'll
 say about this.

0:10:53.100000 --> 0:10:55.920000
 Cisco iOS is massively large.

0:10:55.920000 --> 0:10:59.060000
 If you were actually to take a look at
 all the lines of code in a particular

0:10:59.060000 --> 0:11:03.100000
 iOS software image, there will
 be thousands of lines of code.

0:11:03.100000 --> 0:11:07.940000
 And what some of those lines of code
 do is they instruct the CPU to go

0:11:07.940000 --> 0:11:12.120000
 into an idle state because it's waiting
 for some sort of event or trigger

0:11:12.120000 --> 0:11:17.040000
 to happen, like an incoming data packet
 or an incoming BGP update or a

0:11:17.040000 --> 0:11:19.660000
 TCP keep alive or something
 like that.

0:11:19.660000 --> 0:11:23.180000
 Well that's all well and good if that
 iOS is working on a real physical

0:11:23.180000 --> 0:11:26.820000
 Cisco chassis. The problem
 is it's not.

0:11:26.820000 --> 0:11:30.200000
 In this particular case, it's working
 on an emulated router provided by

0:11:30.200000 --> 0:11:33.460000
 DynaMips and the whole virtualization
 behind this.

0:11:33.460000 --> 0:11:37.180000
 And so when it goes into that idle state,
 it ends up staying in that idle

0:11:37.180000 --> 0:11:41.040000
 state and sort of going into this like
 infinite loop, which can actually

0:11:41.040000 --> 0:11:45.800000
 cause your CPU on your laptop to
 skyrocket and go to like 100%.

0:11:45.800000 --> 0:11:47.580000
 We don't want that.

0:11:47.580000 --> 0:11:51.460000
 So what this does is by clicking this
 button, it's going to sort of go

0:11:51.460000 --> 0:11:55.080000
 through the code in the background and
 look for those particular points

0:11:55.080000 --> 0:11:58.060000
 in the code where that would normally
 happen where it would go into this

0:11:58.060000 --> 0:12:01.720000
 idle state. And instead of telling the
 CPU to go into this idle infinite

0:12:01.720000 --> 0:12:06.380000
 loop, instead it's simply going to
 instruct that virtual router to go

0:12:06.380000 --> 0:12:11.140000
 to sleep. It tells it to go to sleep for
 a few microseconds or a few milliseconds.

0:12:11.140000 --> 0:12:15.000000
 And then it wakes up again and continues
 on to the next task it was going

0:12:15.000000 --> 0:12:19.060000
 to do. So it prevents your CPU from
 going to that skyrocketing 100%.

0:12:19.060000 --> 0:12:22.740000
 So we're going to click
 on the idle PC finder.

0:12:22.740000 --> 0:12:27.740000
 And so you'll get a dialog box, well
 actually a box that looks like this.

0:12:27.740000 --> 0:12:31.780000
 Computing idle PC values and we
 just have to wait patiently.

0:12:31.780000 --> 0:12:32.540000
 It doesn't take very long.

0:12:32.540000 --> 0:12:34.920000
 It's typically less than a minute.


0:12:34.920000 --> 0:12:38.020000
 And then it will come up with
 some value by itself.

0:12:38.020000 --> 0:12:43.640000
 Now there are ways to manually determine
 an idle PC value for the particular

0:12:43.640000 --> 0:12:45.980000
 software that you are using.

0:12:45.980000 --> 0:12:47.880000
 But you shouldn't have to do that.


0:12:47.880000 --> 0:12:53.240000
 This tool should work for you because
 the manual process is rather complex.

0:12:53.240000 --> 0:12:57.540000
 There we go. And it found
 an idle PC value for us.

0:12:57.540000 --> 0:13:02.860000
 And remember this number is unique
 to this particular software image.

0:13:02.860000 --> 0:13:07.320000
 Even if I had another software image
 for this exact same router, but it

0:13:07.320000 --> 0:13:11.420000
 was a different version or a different
 feature set, it would compute a

0:13:11.420000 --> 0:13:13.680000
 different idle PC value.

0:13:13.680000 --> 0:13:16.500000
 So that's why you really don't want
 to do it manually if you can avoid

0:13:16.500000 --> 0:13:19.740000
 it. So now we can hit finish.

0:13:19.740000 --> 0:13:22.080000
 And now that router
 is available to us.

0:13:22.080000 --> 0:13:24.220000
 So now we can use that in
 our virtual topology.

0:13:24.220000 --> 0:13:26.880000
 Now what I'm going to do is I'm going
 to add one more because I also want

0:13:26.880000 --> 0:13:33.020000
 to basically turn this router into a
 switch by selecting the Ether switch

0:13:33.020000 --> 0:13:38.980000
 box. And now when I do that, let's
 go ahead and change the RAM.

0:13:38.980000 --> 0:13:44.680000
 Now you can see that it automatically
 populates one of those slots with

0:13:44.680000 --> 0:13:48.020000
 this 16 port Ether switch module.

0:13:48.020000 --> 0:13:50.180000
 And if you want to, you could
 just leave it that way.

0:13:50.180000 --> 0:13:54.160000
 If the only thing you plan on using this
 router for is a 16 port ethernet

0:13:54.160000 --> 0:13:56.000000
 switch, you could
 leave it that way.

0:13:56.000000 --> 0:13:59.300000
 Or if you want to give yourself more
 flexibility, which is what I like

0:13:59.300000 --> 0:14:02.600000
 to do, let's just go ahead and populate
 those other slots with some other

0:14:02.600000 --> 0:14:08.180000
 stuff. So we've got full flexibility,
 a lot of choices here in how we

0:14:08.180000 --> 0:14:14.100000
 use this thing. Once again, we're
 going to select an idle PC.

0:14:14.100000 --> 0:14:17.420000
 Now what's happening here, I can't show
 it to you because it's actually

0:14:17.420000 --> 0:14:19.220000
 happening on a different monitor.

0:14:19.220000 --> 0:14:23.220000
 But that same box that said, please wait
 computing a value, it's actually

0:14:23.220000 --> 0:14:26.200000
 flashing right now, flashing
 on and off and on and off.

0:14:26.200000 --> 0:14:29.100000
 And the first time I saw that, it kind
 of freaked me out thinking, oh

0:14:29.100000 --> 0:14:30.860000
 my gosh, it's going to
 crash or something.

0:14:30.860000 --> 0:14:35.200000
 But actually, if you just sit back and
 wait, let it keep flashing at you,

0:14:35.200000 --> 0:14:38.940000
 eventually it will compute an
 idle PC value that's suitable.

0:14:38.940000 --> 0:14:43.120000
 So within a few seconds
 here, I should get one.

0:14:43.120000 --> 0:14:46.240000
 There we go. It did find one.

0:14:46.240000 --> 0:14:51.800000
 Finish. And now I have some
 routers available to me.

0:14:51.800000 --> 0:14:54.980000
 So at this point, my setup process is
 done, so now I'm just going to click

0:14:54.980000 --> 0:14:59.820000
 OK. And now it's going to say, OK, what
 do you want the name of your first

0:14:59.820000 --> 0:15:03.440000
 project to be? You probably don't
 want to leave it as untitled.

0:15:03.440000 --> 0:15:04.740000
 So give it some name.

0:15:04.740000 --> 0:15:06.020000
 You can name it whatever you want.


0:15:06.020000 --> 0:15:10.060000
 You could be test or you
 could say OSPF project.

0:15:10.060000 --> 0:15:15.060000
 I'm just going to
 say CCNA, EIGRP1.

0:15:15.060000 --> 0:15:19.400000
 That's just what I'm going
 to call mine and hit OK.

0:15:19.400000 --> 0:15:23.520000
 And now this is your
 main GNS3 window.

0:15:23.520000 --> 0:15:27.020000
 So in the next set of videos, I'm going
 to start talking about how do

0:15:27.020000 --> 0:15:30.120000
 we use this window and what are the various
 icons and what are the various

0:15:30.120000 --> 0:15:32.220000
 menus that are on here.

0:15:32.220000 --> 0:15:34.840000
 So, but for now, we're done
 with the setup process.

0:15:34.840000 --> 0:15:37.240000
 We're done with importing
 our software images.

0:15:37.240000 --> 0:15:40.280000
 Also, one thing I'll show you is that
 you can go back to those routers

0:15:40.280000 --> 0:15:41.720000
 at any point in time.

0:15:41.720000 --> 0:15:46.460000
 You can just hit Edit, Preferences,
 and you're right back here to the

0:15:46.460000 --> 0:15:50.300000
 screen. So just go ahead under
 Dynamips, click on iOS routers.

0:15:50.300000 --> 0:15:55.420000
 There's your routers again, and you
 can go into Edit, and you can change

0:15:55.420000 --> 0:15:57.900000
 a lot of the things
 about these routers.

0:15:57.900000 --> 0:15:59.200000
 For example, the slots.

0:15:59.200000 --> 0:16:02.180000
 I could go back now and change
 them to use different modules.

0:16:02.180000 --> 0:16:05.460000
 Now, you don't want to do this
 while the router is active.

0:16:05.460000 --> 0:16:07.840000
 What we're going to see here in the
 subsequent videos is it's going to

0:16:07.840000 --> 0:16:11.340000
 be a process of dragging your
 router into the main screen.

0:16:11.340000 --> 0:16:14.100000
 But once you do that, it's like
 the router is shut down.

0:16:14.100000 --> 0:16:15.080000
 It's not active.

0:16:15.080000 --> 0:16:18.400000
 And then we're going to click a button
 to start up the router, which is

0:16:18.400000 --> 0:16:20.160000
 sort of like powering it on.

0:16:20.160000 --> 0:16:24.180000
 Once a router is powered on, you don't
 want to go in here and try to change

0:16:24.180000 --> 0:16:27.740000
 the modules. I haven't tried doing that,
 but it would probably be a bad

0:16:27.740000 --> 0:16:30.300000
 thing. Your laptop would probably
 blow up in your face.

0:16:30.300000 --> 0:16:31.700000
 Well, maybe not that.

0:16:31.700000 --> 0:16:36.160000
 But it certainly might crash the system
 or have other unintended effects.

0:16:36.160000 --> 0:16:39.980000
 So, if you're going to change what's
 in your module slots or change the

0:16:39.980000 --> 0:16:43.240000
 amount of memory allocated to your
 router or something like that, you

0:16:43.240000 --> 0:16:45.960000
 want to make sure that all your routers
 are shut down and they're not

0:16:45.960000 --> 0:16:48.340000
 working to do that.

0:16:48.340000 --> 0:16:51.660000
 So that completes this section of
 the video on the setup process.

0:16:51.660000 --> 0:16:54.480000
 In the next set of videos, we're going
 to go into how to actually use

0:16:54.480000 --> 0:16:56.860000
 this to build our virtual
 topologies.

