WEBVTT

0:00:08.280000 --> 0:00:12.240000
 So in this video, which is continuing
 our discussion about making sure

0:00:12.240000 --> 0:00:16.860000
 you select an iOS software image that
 will fit your needs within GNS3,

0:00:16.860000 --> 0:00:19.980000
 the next thing we're going to talk
 about is memory considerations.

0:00:19.980000 --> 0:00:22.100000
 Now what do I mean by that?

0:00:22.100000 --> 0:00:25.320000
 Cisco iOS software, just like anything
 else that you download, whether

0:00:25.320000 --> 0:00:29.840000
 it be another web browser or an email client
 or an instant messaging program,

0:00:29.840000 --> 0:00:33.300000
 they all take up memory
 within your laptop.

0:00:33.300000 --> 0:00:36.360000
 And I'm presuming you're using some
 sort of laptop or possibly a server

0:00:36.360000 --> 0:00:40.940000
 to run GNS3. And the memory that you
 have available on your laptop is

0:00:40.940000 --> 0:00:43.100000
 a constrained resource, right?

0:00:43.100000 --> 0:00:45.400000
 You only have so much
 of it to go around.

0:00:45.400000 --> 0:00:48.580000
 And this is something to think about
 when selecting a Cisco iOS software

0:00:48.580000 --> 0:00:50.660000
 image for two reasons.

0:00:50.660000 --> 0:00:54.380000
 Number one, we want to make sure if
 we have a choice, once again, you

0:00:54.380000 --> 0:00:55.940000
 might not have a choice.

0:00:55.940000 --> 0:01:00.220000
 But if you have a choice among different
 images that you can use, if one

0:01:00.220000 --> 0:01:07.560000
 image requires significantly larger
 memory to run than another image,

0:01:07.560000 --> 0:01:11.180000
 it might be in your best interest to
 select that other image that requires

0:01:11.180000 --> 0:01:15.380000
 less memory for number one
 for your laptop, right?

0:01:15.380000 --> 0:01:17.040000
 It's going to save memory
 in your laptop.

0:01:17.040000 --> 0:01:20.360000
 The more routers that you have open
 and running, the more memory it's

0:01:20.360000 --> 0:01:24.440000
 going to chew up on your laptop, the
 more resources it's going to consume.

0:01:24.440000 --> 0:01:28.380000
 Another thing about memory considerations
 is when you actually go to import

0:01:28.380000 --> 0:01:32.080000
 the software image
 into GNS3 itself.

0:01:32.080000 --> 0:01:37.020000
 Part of adding a new software image
 to GNS3, telling GNS3, this is what

0:01:37.020000 --> 0:01:41.400000
 I want to use. Part of that process
 is GNS3 will ask you how much memory

0:01:41.400000 --> 0:01:46.260000
 do you want to allocate for each router
 that's using this software.

0:01:46.260000 --> 0:01:50.280000
 Now if you do too much memory, it's
 not going to hurt the router, but

0:01:50.280000 --> 0:01:54.280000
 certainly going to run out
 of memory that much faster.

0:01:54.280000 --> 0:01:56.680000
 You won't be able to create
 larger topologies.

0:01:56.680000 --> 0:02:01.260000
 On the flip side, if you allocate too
 little memory to that software,

0:02:01.260000 --> 0:02:05.300000
 well now your routers might either
 not start up at all, or they might

0:02:05.300000 --> 0:02:09.180000
 start up with a whole bunch of errors
 and trace back messages, or they

0:02:09.180000 --> 0:02:12.320000
 might start up, they might run for
 a little while, and then you go to

0:02:12.320000 --> 0:02:15.660000
 turn on some new feature protocol and
 bang, now you start getting trace

0:02:15.660000 --> 0:02:17.320000
 back messages and errors.

0:02:17.320000 --> 0:02:21.580000
 So we want to make sure that we're mindful
 of memory in those two circumstances.

0:02:21.580000 --> 0:02:24.800000
 How much memory this particular image
 is going to chew up in my laptop

0:02:24.800000 --> 0:02:29.680000
 every time I open up a router, and how
 much memory does a software image

0:02:29.680000 --> 0:02:32.520000
 take? How do I know
 the answer to that?

0:02:32.520000 --> 0:02:36.480000
 So when I'm importing it into GNS3,
 I can select the correct amount of

0:02:36.480000 --> 0:02:39.240000
 memory. So let's look at
 these to begin with.

0:02:39.240000 --> 0:02:47.660000
 So let's say that I
 had available to me.

0:02:47.660000 --> 0:02:53.980000
 Let's say I had, so here I have, I'm fortunate,
 and I have several versions

0:02:53.980000 --> 0:02:55.660000
 of software available to me.

0:02:55.660000 --> 0:02:58.820000
 So maybe I say, okay, well let's
 see, how about the 7200 here?

0:02:58.820000 --> 0:03:02.080000
 I know there's lots of different port
 adapters that go with 7200, so that's

0:03:02.080000 --> 0:03:06.500000
 going to give me a lot of choices as
 far as what kinds of interfaces I

0:03:06.500000 --> 0:03:10.520000
 want. Well, if I'm going to use that,
 first thing I'm going to have to

0:03:10.520000 --> 0:03:13.440000
 know is how much memory is
 that going to consume?

0:03:13.440000 --> 0:03:16.440000
 I don't know the answer to that at
 the top of my head, so I'll go back

0:03:16.440000 --> 0:03:22.020000
 to our trusty Cisco feature navigator
 and research software.

0:03:22.020000 --> 0:03:27.460000
 And once again, research it by platform
 and iOS because I know that this

0:03:27.460000 --> 0:03:30.420000
 was a 7200 image I'm
 interested in.

0:03:30.420000 --> 0:03:35.060000
 So from my platform, I'll
 find 7200 here in my list.

0:03:35.060000 --> 0:03:38.660000
 Here we go, 7200.

0:03:38.660000 --> 0:03:45.060000
 And that particular image
 was mainline 12.233.

0:03:45.060000 --> 0:03:52.300000
 It's 12233 SRE. So 12, and let me just
 zoom in on here in case you weren't

0:03:52.300000 --> 0:03:53.380000
 able to see that.

0:03:53.380000 --> 0:03:56.860000
 This is the image I'm looking
 up right now, the 7200 series.

0:03:56.860000 --> 0:04:01.640000
 12233 SRE. All right, so
 let's just go down here.

0:04:01.640000 --> 0:04:07.060000
 So 12200. And here is SRE.

0:04:07.060000 --> 0:04:12.960000
 And my particular
 one is 12233 SRE3.

0:04:12.960000 --> 0:04:17.640000
 So 12233 SRE3. There we go.

0:04:17.640000 --> 0:04:22.320000
 And the features that I have
 is advanced enterprise K9.

0:04:22.320000 --> 0:04:26.420000
 Here we go, advanced enterprise.

0:04:26.420000 --> 0:04:30.040000
 All right, so it tells
 me right here.

0:04:30.040000 --> 0:04:33.820000
 The minimum DRAM or flash, mostly I'm
 concerned with DRAM because when

0:04:33.820000 --> 0:04:38.140000
 this router is running, it's DRAM memory
 that's going to be used for storing

0:04:38.140000 --> 0:04:42.640000
 the iOS image, creating my ARP tables
 and routing tables and all that

0:04:42.640000 --> 0:04:48.480000
 stuff. So you can see a single router
 is going to use up 512 megabytes

0:04:48.480000 --> 0:04:51.260000
 of DRAM memory. That's a lot.

0:04:51.260000 --> 0:04:56.120000
 So I better have a lot of memory on
 my laptop to be able to handle that.

0:04:56.120000 --> 0:04:59.220000
 Well, you might be saying, well, but
 Keith, I don't even really know how

0:04:59.220000 --> 0:05:00.980000
 much memory I do have
 on my laptop.

0:05:00.980000 --> 0:05:02.520000
 How do I figure that out?

0:05:02.520000 --> 0:05:06.300000
 Well, what you can do is now I'm
 just doing this based on Windows.

0:05:06.300000 --> 0:05:09.200000
 Of course, if you're using a Mac or
 Linux or something else, it would

0:05:09.200000 --> 0:05:13.400000
 be different. But in Windows, if you
 click on your start button and then

0:05:13.400000 --> 0:05:16.780000
 somewhere in there, you'll find computer
 or possibly my computer.

0:05:16.780000 --> 0:05:21.360000
 And if you right click on that and
 select properties, you'll get a box

0:05:21.360000 --> 0:05:23.140000
 that looks like this.

0:05:23.140000 --> 0:05:27.700000
 And in my particular case, you can see
 that my particular laptop has basically

0:05:27.700000 --> 0:05:32.160000
 about eight gigs of RAM available.


0:05:32.160000 --> 0:05:37.200000
 So if each one of those 7200 series
 routers was using about 500 megs,

0:05:37.200000 --> 0:05:41.240000
 that means just two routers
 are using one gig.

0:05:41.240000 --> 0:05:45.040000
 And remember, the GNS3 application itself
 is going to consume some memory

0:05:45.040000 --> 0:05:49.800000
 and Windows is going to consume some memory
 just to do the operating system.

0:05:49.800000 --> 0:05:52.540000
 So probably not going to be able to
 have a whole lot of routers here if

0:05:52.540000 --> 0:05:54.540000
 I'm using the 7200 series.

0:05:54.540000 --> 0:05:55.820000
 But let's go ahead and try it.

0:05:55.820000 --> 0:05:57.820000
 Let's see what that looks like.

0:05:57.820000 --> 0:06:00.440000
 So I'll go now into GNS3.

0:06:00.440000 --> 0:06:03.120000
 I've got open already.

0:06:03.120000 --> 0:06:07.580000
 And this particular project here is called
 just test so that we can reference

0:06:07.580000 --> 0:06:09.460000
 it later on, my test project.

0:06:09.460000 --> 0:06:15.360000
 And I'll go under edit, preferences,
 and then under dynamics, click on

0:06:15.360000 --> 0:06:19.980000
 iOS routers. And here is where
 you actually add your iOS.

0:06:19.980000 --> 0:06:21.980000
 I'll get into this in another
 video in just a second.

0:06:21.980000 --> 0:06:25.160000
 We're going to go through the whole walkthrough
 process about downloading

0:06:25.160000 --> 0:06:27.540000
 the software and setting stuff up.


0:06:27.540000 --> 0:06:31.360000
 But just to sort of like a little preview
 here, I'll go ahead and do new.

0:06:31.360000 --> 0:06:35.520000
 And I'll find that iOS image
 where it's located.

0:06:35.520000 --> 0:06:38.920000
 Here it is. Click open.

0:06:38.920000 --> 0:06:40.580000
 I'll say yes, I want
 to decompress it.

0:06:40.580000 --> 0:06:43.180000
 And don't worry if I'm going a little
 fast for you because we're going

0:06:43.180000 --> 0:06:44.720000
 to walk through all these
 steps coming up.

0:06:44.720000 --> 0:06:48.460000
 The main reason I'm showing this to
 you is because I want to show you

0:06:48.460000 --> 0:06:50.940000
 how much memory this thing uses.

0:06:50.940000 --> 0:06:53.820000
 Now right here, default RAM.

0:06:53.820000 --> 0:06:57.680000
 Because I've already used GNS3 several
 times before recording this video

0:06:57.680000 --> 0:07:01.940000
 and because I've used it with this image,
 it actually remembered how much

0:07:01.940000 --> 0:07:05.140000
 RAM it takes. You might be saying, oh,
 it's smart enough to figure that

0:07:05.140000 --> 0:07:06.640000
 out. No, it's not.

0:07:06.640000 --> 0:07:10.720000
 When I did this the very first time,
 it defaulted to a RAM size of about

0:07:10.720000 --> 0:07:16.140000
 128 megabits, which clearly are megabytes,
 which clearly would not be

0:07:16.140000 --> 0:07:19.920000
 nearly enough. So just make sure that
 this number right here is the same

0:07:19.920000 --> 0:07:24.120000
 number that you found on the
 Cisco feature navigator.

0:07:24.120000 --> 0:07:27.260000
 Now, just a little word
 about that as well.

0:07:27.260000 --> 0:07:29.980000
 So in the Cisco feature navigator,
 when it gives you that number, like

0:07:29.980000 --> 0:07:34.740000
 this image requires 512 megabytes
 or 256 megabytes.

0:07:34.740000 --> 0:07:38.420000
 Where they really come up with that
 number is they say, if you had that

0:07:38.420000 --> 0:07:42.540000
 image running on your router and you
 had everything going, every possible

0:07:42.540000 --> 0:07:46.220000
 feature and every possible protocol
 that this router could support, if

0:07:46.220000 --> 0:07:50.380000
 they were all running, this is
 how much memory you would need.

0:07:50.380000 --> 0:07:54.460000
 Now, chances are when you're doing your
 GNS3 topology, you're not going

0:07:54.460000 --> 0:07:57.840000
 to be having every single thing running
 that the software could potentially

0:07:57.840000 --> 0:08:01.780000
 support. So in reality, when you're
 allocating your memory right here,

0:08:01.780000 --> 0:08:05.940000
 you probably could get away with doing
 a little bit less than what the

0:08:05.940000 --> 0:08:07.820000
 software actually requires.

0:08:07.820000 --> 0:08:10.480000
 Which is kind of nice because if you're
 actually loading the software

0:08:10.480000 --> 0:08:15.880000
 on a real Cisco router, it wouldn't even
 load if it didn't have that amount

0:08:15.880000 --> 0:08:19.300000
 of RAM. But here, because we're emulating
 these routers, I could get away

0:08:19.300000 --> 0:08:21.380000
 with a little bit less
 if I wanted to.

0:08:21.380000 --> 0:08:23.860000
 But for the purposes of this demonstration,
 I'm just going to leave it

0:08:23.860000 --> 0:08:28.360000
 to match the same number we saw in the
 feature navigator and click Next.

0:08:28.360000 --> 0:08:31.560000
 I don't really care what
 I'm populating this with.

0:08:31.560000 --> 0:08:33.980000
 For the purposes of this demonstration,
 that's not really relevant.

0:08:33.980000 --> 0:08:39.820000
 So I'll just populate some slots here,
 find an idle PC, and we'll talk

0:08:39.820000 --> 0:08:43.020000
 about idle PC also coming
 up in a future video.

0:08:43.020000 --> 0:08:47.700000
 This is basically a way to ensure that
 GNS3 and the emulated routers within

0:08:47.700000 --> 0:08:53.760000
 it don't completely hog and use up,
 as it says, 100% of your CPU.

0:08:53.760000 --> 0:08:56.780000
 Because if that happens, then your
 laptop will just freeze and nothing

0:08:56.780000 --> 0:09:01.020000
 will work. So computing these idle PC
 gives us a number to prevent that

0:09:01.020000 --> 0:09:03.200000
 kind of situation from happening.

0:09:03.200000 --> 0:09:08.020000
 And in just a couple of seconds here,
 we should get an idle PC value for

0:09:08.020000 --> 0:09:09.900000
 that particular software.

0:09:09.900000 --> 0:09:13.380000
 And each software image
 is different.

0:09:13.380000 --> 0:09:17.680000
 Right now I'm doing it for a 7200 series,
 but even if I had another 7200

0:09:17.680000 --> 0:09:22.420000
 series software that was a different
 feature set or a different version,

0:09:22.420000 --> 0:09:24.720000
 it would come up with a
 different idle PC value.

0:09:24.720000 --> 0:09:26.420000
 They're all different.

0:09:26.420000 --> 0:09:30.400000
 Okay, finish. So now we can see the
 7200 is available here for me.

0:09:30.400000 --> 0:09:33.560000
 Alright, so let's just go
 ahead and apply that.

0:09:33.560000 --> 0:09:36.820000
 Okay, now let's just create
 a real simple project.

0:09:36.820000 --> 0:09:42.740000
 Now, before I do anything, we can see
 that if I bring this up, so what

0:09:42.740000 --> 0:09:49.120000
 GNS3 does by default is within your
 C drive, within your users folder,

0:09:49.120000 --> 0:09:52.420000
 and then your name, whatever it is,
 you'll see a GNS3 folder and then

0:09:52.420000 --> 0:09:54.420000
 a subfolder called projects.

0:09:54.420000 --> 0:09:57.600000
 And you can see that
 test is in there.

0:09:57.600000 --> 0:10:03.160000
 Now, right now, I have not added
 any routers to this project.

0:10:03.160000 --> 0:10:05.580000
 There's really nothing running, so
 you can see when I just hover over

0:10:05.580000 --> 0:10:08.920000
 it, that project, which is pretty much
 doing nothing right now, is using

0:10:08.920000 --> 0:10:11.900000
 about 74.2 megabytes.

0:10:11.900000 --> 0:10:15.360000
 Alright, let's see how that number changes
 as I start pulling some routers

0:10:15.360000 --> 0:10:17.660000
 into my project.

0:10:17.660000 --> 0:10:21.620000
 So, let's go ahead and open this up,
 and let's just pull a single 7200

0:10:21.620000 --> 0:10:24.820000
 series. Now, I haven't
 started it yet.

0:10:24.820000 --> 0:10:27.080000
 This router is sort of like
 in a powered down state.

0:10:27.080000 --> 0:10:30.000000
 It's there in the image,
 but it's not running yet.

0:10:30.000000 --> 0:10:31.800000
 Did that actually change
 anything in my project?

0:10:31.800000 --> 0:10:33.720000
 Let's hover it over it again.

0:10:33.720000 --> 0:10:37.200000
 Nope, still 74.2 megs.

0:10:37.200000 --> 0:10:39.860000
 Okay, so that hasn't
 changed anything.

0:10:39.860000 --> 0:10:44.940000
 So, let's just go ahead and add in, let's
 just start with that one router.

0:10:44.940000 --> 0:10:47.200000
 So now I'm going to go
 ahead and turn it on.

0:10:47.200000 --> 0:10:50.320000
 Remember, we were at 74
.2 megs before, right?

0:10:50.320000 --> 0:10:53.660000
 Now the router is running,
 one instance of a 7200.

0:10:53.660000 --> 0:10:57.720000
 Now, instead of 74.2 megs,
 what are we up to now?

0:10:57.720000 --> 0:11:03.460000
 Well, it still says 74.2, but
 I find that highly suspicious.

0:11:03.460000 --> 0:11:10.420000
 Let's go into our projects file,
 dynamips, and here we can see.

0:11:10.420000 --> 0:11:16.700000
 Okay, so we've got, here's my iOS image,
 and we can see it's using roughly

0:11:16.700000 --> 0:11:19.860000
 262 megs right now.

0:11:19.860000 --> 0:11:24.240000
 Now this is called a ghost file, we can
 also see up here the input output

0:11:24.240000 --> 0:11:27.160000
 memory of 262 megabytes.

0:11:27.160000 --> 0:11:28.420000
 That's one router.

0:11:28.420000 --> 0:11:30.860000
 Let's add a second router.

0:11:30.860000 --> 0:11:36.820000
 Let's bring a second router of the exact
 same type, 7200, into the mix.

0:11:36.820000 --> 0:11:38.360000
 I'm not going to connect
 them or anything.

0:11:38.360000 --> 0:11:40.460000
 I'm going to go ahead
 and start that guy up.

0:11:40.460000 --> 0:11:45.960000
 Start. Okay, so let's go back.

0:11:45.960000 --> 0:11:47.360000
 Now, look at this.

0:11:47.360000 --> 0:11:55.120000
 Now we have, if I zoom in on this a little
 bit, we have 262 megs for 7200

0:11:55.120000 --> 0:12:01.320000
 I3 and another 262
 megs for 7200 I2.

0:12:01.320000 --> 0:12:04.820000
 So you can see it's starting to
 consume quite a bit more memory.

0:12:04.820000 --> 0:12:08.520000
 Each time I open up a new router and
 I start it, it's consuming another

0:12:08.520000 --> 0:12:14.740000
 262 megs within my
 projects folder.

0:12:14.740000 --> 0:12:20.180000
 Now once I go back and I stop these
 guys, don't need them anymore, so

0:12:20.180000 --> 0:12:29.380000
 stop them. Go back to users and you
 can see now those files are gone.

0:12:29.380000 --> 0:12:33.580000
 The only file that's left is the ghost
 file of 262 megs, but those other

0:12:33.580000 --> 0:12:38.380000
 IO memory files that we're
 consuming a lot are gone.

0:12:38.380000 --> 0:12:40.960000
 Now you might be thinking, okay, well
 is that going to be the case with

0:12:40.960000 --> 0:12:42.780000
 every router that I have?

0:12:42.780000 --> 0:12:45.400000
 Well, not necessarily,
 for example.

0:12:45.400000 --> 0:12:49.760000
 In this particular project, let me go ahead
 and get rid of these two routers.

0:12:49.760000 --> 0:12:54.700000
 Delete. Yes. Right click delete.

0:12:54.700000 --> 0:13:00.360000
 Yes. Now let's instead, let's use a 3725
 which I already imported in here.

0:13:00.360000 --> 0:13:04.140000
 Okay, let's turn one of these on.

0:13:04.140000 --> 0:13:10.960000
 Start. Let's go back to
 my projects folder.

0:13:10.960000 --> 0:13:14.500000
 Okay, let's refresh
 this a little bit.

0:13:14.500000 --> 0:13:20.120000
 Refresh. Okay, so now at this point,
 if I zoom in, we can see that I have

0:13:20.120000 --> 0:13:22.840000
 a ghost file. It always creates
 a single ghost file.

0:13:22.840000 --> 0:13:25.600000
 It sort of represents that
 iOS image it's using.

0:13:25.600000 --> 0:13:28.500000
 So whether you've got two routers or
 five routers or ten routers, there's

0:13:28.500000 --> 0:13:31.140000
 going to be one ghost file
 for that particular iOS.

0:13:31.140000 --> 0:13:35.100000
 So there it is, 262 megs.

0:13:35.100000 --> 0:13:36.440000
 And let's see here.

0:13:36.440000 --> 0:13:43.260000
 Don't really see any IOMEM
 file for the 3725.

0:13:43.260000 --> 0:13:46.940000
 I just see really, this is really
 the single largest file right now.

0:13:46.940000 --> 0:13:49.340000
 Now it also has the 7200 in here.

0:13:49.340000 --> 0:13:53.240000
 That's sort of like a carryover from
 when I had the 7200 in there.

0:13:53.240000 --> 0:13:56.080000
 As a matter of fact, let's just
 get rid of all of that.

0:13:56.080000 --> 0:13:59.260000
 So here's what I'm going to do
 to make it nice and simple.

0:13:59.260000 --> 0:14:05.200000
 I'm going to stop the router, close
 up shop, quit, yep, discard.

0:14:05.200000 --> 0:14:06.840000
 I don't want any changes.

0:14:06.840000 --> 0:14:09.100000
 All right, let's go ahead
 and restart GNS3 again.

0:14:09.100000 --> 0:14:11.860000
 I'm just trying to show you how this
 affects the memory of your laptop

0:14:11.860000 --> 0:14:14.040000
 as I do these various things.

0:14:14.040000 --> 0:14:19.080000
 Okay, let's go ahead and
 title it test two.

0:14:19.080000 --> 0:14:24.460000
 Okay, edit preferences, routers.

0:14:24.460000 --> 0:14:27.300000
 Okay, so for test two, I'm going to
 say, oh, I don't want the 7200 at

0:14:27.300000 --> 0:14:29.620000
 all. So let's just get
 rid of that image.

0:14:29.620000 --> 0:14:35.820000
 Apply, okay. All right, so let's
 bring a 3725 into the mix.

0:14:35.820000 --> 0:14:40.120000
 Start it up. Okay, so
 we have one router.

0:14:40.120000 --> 0:14:43.560000
 By this time, it's a different
 router, a 3725 router.

0:14:43.560000 --> 0:14:48.780000
 Now when we go into test two project,
 there it is, and go into our project

0:14:48.780000 --> 0:14:51.480000
 files, dynamips.

0:14:51.480000 --> 0:14:57.640000
 We can see with that 3725 that is currently
 running right now, the single

0:14:57.640000 --> 0:15:02.520000
 largest file we have is our ghost file
 for that particular software image.

0:15:02.520000 --> 0:15:05.880000
 That's it. Now remember, what did
 we see with the 7200 series?

0:15:05.880000 --> 0:15:10.680000
 When I opened up a second router, with
 just one 7200, not only did we

0:15:10.680000 --> 0:15:15.740000
 have the ghost file, we also had this
 really large IOMEM file for the

0:15:15.740000 --> 0:15:18.820000
 7200 that was basically
 the same size.

0:15:18.820000 --> 0:15:23.680000
 And every time I opened a second 7200,
 and then a third 7200, that created

0:15:23.680000 --> 0:15:26.360000
 another IOMEM file for that.

0:15:26.360000 --> 0:15:30.760000
 But notice, no IOMEM files
 here for this 3725.

0:15:30.760000 --> 0:15:34.020000
 Let's go ahead and open up a second
 instance of that router.

0:15:34.020000 --> 0:15:35.820000
 Let's go ahead and
 drag and drop it.

0:15:35.820000 --> 0:15:38.460000
 Let's start it up.

0:15:38.460000 --> 0:15:44.780000
 There we go. Go back to our file.

0:15:44.780000 --> 0:15:49.940000
 And notice once again, we only have
 one large file, just the ghost file.

0:15:49.940000 --> 0:15:53.760000
 We don't have those really large IOMEM
 files that we're seeing that we

0:15:53.760000 --> 0:15:57.220000
 were seeing with the 7200 series.

0:15:57.220000 --> 0:15:59.440000
 So, what's the takeaway
 from all this?

0:15:59.440000 --> 0:16:01.100000
 We've talked about a lot of stuff.


0:16:01.100000 --> 0:16:05.440000
 The takeaway from this is, number one,
 when you are importing your router,

0:16:05.440000 --> 0:16:10.160000
 your software images into GNS3, some
 of those software images, like for

0:16:10.160000 --> 0:16:16.160000
 the 7200 series, every time you start
 a new router, it takes up a gob

0:16:16.160000 --> 0:16:17.920000
 of memory in your laptop.

0:16:17.920000 --> 0:16:21.980000
 We saw that with the 7200 series, and
 I just had two routers in my topology.

0:16:21.980000 --> 0:16:27.100000
 Other software images, like the 3725,
 you can start up three, four, five,

0:16:27.100000 --> 0:16:30.880000
 six instances of those routers, but
 you're only going to have one large

0:16:30.880000 --> 0:16:33.040000
 ghost file representing
 the software.

0:16:33.040000 --> 0:16:36.020000
 You're not going to have multiple instances
 of other files, like these

0:16:36.020000 --> 0:16:41.080000
 IOMEM files. So, that's really going
 to conserve memory in your laptop.

0:16:41.080000 --> 0:16:43.900000
 And the other thing we talked about was,
 when you're importing a software

0:16:43.900000 --> 0:16:47.800000
 image into GNS3, one of the things that's
 going to ask you is, how much

0:16:47.800000 --> 0:16:49.800000
 memory do you want to allocate
 for this router?

0:16:49.800000 --> 0:16:54.240000
 As a good rule of thumb, it's a good
 idea to know in advance how much

0:16:54.240000 --> 0:16:58.560000
 memory that router image needs based
 on the Cisco feature navigator.

0:16:58.560000 --> 0:17:03.460000
 And once you have that, allocate that same
 amount into GNS3 for that particular

