WEBVTT

0:00:08.560000 --> 0:00:12.320000
 In this video, I want to introduce you
 to the concept of connecting your

0:00:12.320000 --> 0:00:18.600000
 GNS3 simulated network to an actual live
 external network or live external

0:00:18.600000 --> 0:00:21.020000
 device. It doesn't have
 to be a network.

0:00:21.020000 --> 0:00:25.720000
 Maybe you want to take your GNS3 topology
 and you want to practice AAA,

0:00:25.720000 --> 0:00:29.560000
 you want to practice RADIUS, but you
 need a RADIUS server to do that.

0:00:29.560000 --> 0:00:32.920000
 Maybe you've actually got another laptop
 or a server sitting right on

0:00:32.920000 --> 0:00:37.640000
 your desk that actually has a RADIUS
 server application running in it

0:00:37.640000 --> 0:00:42.540000
 and you want to connect that to your
 simulated topology and GNS3.

0:00:42.540000 --> 0:00:46.940000
 Or more likely if you're like a CCNA
 or CCNP student, you probably want

0:00:46.940000 --> 0:00:50.260000
 to practice some of those switching
 commands that are not available in

0:00:50.260000 --> 0:01:02.360000
 the Ether switch module or
 in the built-in system.

0:01:02.360000 --> 0:01:22.620000
 So, let's go ahead and take a look at
 what I'm actually going to be doing.

0:01:22.620000 --> 0:01:25.660000
 So, this right here represents
 the same type of network.

0:01:25.660000 --> 0:01:26.740000
 So, this right here represents
 the same type of network.

0:01:26.740000 --> 0:01:29.280000
 My actual layout,
 my topology here.

0:01:29.280000 --> 0:01:35.400000
 So, this is my laptop and this right
 here is an actual physical switch

0:01:35.400000 --> 0:01:37.500000
 I have sitting next to me.

0:01:37.500000 --> 0:01:40.600000
 And I've got that physical switch turned
 on right now and I have a real

0:01:40.600000 --> 0:01:46.220000
 ethernet cable connecting one of the
 ports of that switch into the actual

0:01:46.220000 --> 0:01:48.820000
 ethernet knit card of my laptop.

0:01:48.820000 --> 0:01:49.860000
 So, that's how I'm doing this.

0:01:49.860000 --> 0:01:53.940000
 Now, with GNS3, you actually could even
 use your Wi-Fi knit card and connect

0:01:53.940000 --> 0:01:56.260000
 it via Wi-Fi. Now, certainly you're
 not going to be able to do that to

0:01:56.260000 --> 0:01:57.740000
 connect to a switch.

0:01:57.740000 --> 0:02:01.600000
 But if you want to connect to a physical
 device like a switch or a server,

0:02:01.600000 --> 0:02:06.760000
 key point is you take that physical
 device, whatever it is, in this case

0:02:06.760000 --> 0:02:12.640000
 a switch, connect it via a real physical
 ethernet cable into the knit

0:02:12.640000 --> 0:02:16.960000
 card of whatever laptop or device it
 is where you're actually running

0:02:16.960000 --> 0:02:22.260000
 GNS3. Now, here within GNS3, I've got
 GNS3 up and running and I've got

0:02:22.260000 --> 0:02:24.420000
 my virtual topology built.

0:02:24.420000 --> 0:02:27.700000
 And here's how we're going to
 connect all this together.

0:02:27.700000 --> 0:02:33.680000
 I'm going to use one of the built-in
 nodes within GNS3 called the cloud

0:02:33.680000 --> 0:02:39.600000
 node. Now let me preface this by saying
 I could also select the host node,

0:02:39.600000 --> 0:02:41.600000
 cloud node, host node.

0:02:41.600000 --> 0:02:44.120000
 They both do exactly
 the same thing.

0:02:44.120000 --> 0:02:47.120000
 And in just a moment I'll talk about
 why you might want to use one over

0:02:47.120000 --> 0:02:51.400000
 the other. And so once I have the cloud
 node in there, I'm going to configure

0:02:51.400000 --> 0:02:56.020000
 that cloud node so that it recognizes
 that it should connect externally

0:02:56.020000 --> 0:02:59.620000
 to my actual knit card.

0:02:59.620000 --> 0:03:02.220000
 So I'm going to configure the cloud
 node and also if you were using the

0:03:02.220000 --> 0:03:04.140000
 host node, same thing.

0:03:04.140000 --> 0:03:09.200000
 Make it realize via configuration that's
 connecting to your LAN adapter,

0:03:09.200000 --> 0:03:14.140000
 your knit card. And then after that's
 done using just the regular add

0:03:14.140000 --> 0:03:18.840000
 a link tool that's within GNS3, I'm
 just going to add a link between the

0:03:18.840000 --> 0:03:23.680000
 fast ethernet port of my
 router into the cloud.

0:03:23.680000 --> 0:03:26.880000
 And so by this cloud node here, this is
 going to be the thing that's actually

0:03:26.880000 --> 0:03:30.360000
 going to connect my simulated environment
 to my real physical hardware

0:03:30.360000 --> 0:03:34.180000
 on the outside. So how do
 we go ahead and do that?

0:03:34.180000 --> 0:03:36.820000
 So like I said, I've already
 got the physical piece done.

0:03:36.820000 --> 0:03:38.440000
 I've got the switch powered on.

0:03:38.440000 --> 0:03:42.160000
 I've got the switch physically cabled
 into the ethernet port on the back

0:03:42.160000 --> 0:03:45.340000
 of my laptop. And I've
 got the switch running.

0:03:45.340000 --> 0:03:48.620000
 Right now I've changed the host name
 to Keith's switch just to make it

0:03:48.620000 --> 0:03:53.020000
 unique. So at that point,
 I'm going to go into GNS3.

0:03:53.020000 --> 0:03:56.460000
 And just to make this super simple, I'm
 just going to use a single router.

0:03:56.460000 --> 0:04:00.040000
 I don't need to have a real big topology
 in order to demonstrate the fundamental

0:04:00.040000 --> 0:04:05.460000
 concept here. And so now I'm going to
 click on right here, this part here,

0:04:05.460000 --> 0:04:07.820000
 which is the browse end devices.

0:04:07.820000 --> 0:04:10.100000
 And you'll see I've
 got cloud in here.

0:04:10.100000 --> 0:04:13.240000
 So just drag and drop that
 into your topology.

0:04:13.240000 --> 0:04:15.420000
 And now right click on cloud.

0:04:15.420000 --> 0:04:19.420000
 There's no command line interface for
 this, just like how the ethernet

0:04:19.420000 --> 0:04:22.740000
 switch didn't have a command line
 and other the frame relay switch.

0:04:22.740000 --> 0:04:26.740000
 So you're just going to use
 the configure button here.

0:04:26.740000 --> 0:04:31.880000
 And now here, under ethernet,
 you've got various options.

0:04:31.880000 --> 0:04:35.880000
 So what this is saying is, okay, how
 is the cloud node going to connect

0:04:35.880000 --> 0:04:37.020000
 to the outside world?

0:04:37.020000 --> 0:04:40.100000
 And if you select this dropdown box,
 I could have it connect the outside

0:04:40.100000 --> 0:04:43.000000
 world via my Wi-Fi card.

0:04:43.000000 --> 0:04:46.240000
 In some scenarios, it
 might research online.

0:04:46.240000 --> 0:04:49.360000
 They recommend configuring a loopback
 adapter and then connecting your

0:04:49.360000 --> 0:04:53.140000
 cloud to that. But in my particular case,
 I'm just going to have my cloud

0:04:53.140000 --> 0:04:56.160000
 connect to my local
 area connection.

0:04:56.160000 --> 0:04:58.620000
 This is my LAN adapter.

0:04:58.620000 --> 0:05:02.620000
 And then I'll click add.

0:05:02.620000 --> 0:05:08.560000
 And then at that point,
 I just click apply.

0:05:08.560000 --> 0:05:14.320000
 And then okay. So now my cloud knows
 how it's supposed to connect external

0:05:14.320000 --> 0:05:19.380000
 to my laptop. In other words, what physical
 net card on my laptop should

0:05:19.380000 --> 0:05:20.160000
 it be connected to?

0:05:20.160000 --> 0:05:24.440000
 So now it's just simply a matter of
 using the add a link tool, go to my

0:05:24.440000 --> 0:05:27.780000
 router, select his
 fast ethernet link.

0:05:27.780000 --> 0:05:29.700000
 You're going to have to
 do this via ethernet.

0:05:29.700000 --> 0:05:34.020000
 You can't select a serial interface
 or anything and connect it to the

0:05:34.020000 --> 0:05:38.140000
 local area connection right here
 that you see within the cloud.

0:05:38.140000 --> 0:05:40.120000
 Okay, deselect that.

0:05:40.120000 --> 0:05:43.800000
 Now at this point, before I go any further,
 I know that this cloud really

0:05:43.800000 --> 0:05:46.440000
 represents a switch that
 I'm connected to.

0:05:46.440000 --> 0:05:50.140000
 So I can actually right click on the
 cloud and click right here where

0:05:50.140000 --> 0:05:52.500000
 it says change symbol.

0:05:52.500000 --> 0:05:54.100000
 And I'm going to go ahead
 and scroll down.

0:05:54.100000 --> 0:05:56.380000
 And I know that that's actually connected
 to a multi-layer switch.

0:05:56.380000 --> 0:05:59.000000
 I've got a 3750 sitting
 next to me right here.

0:05:59.000000 --> 0:06:02.980000
 So I'll actually change the icon
 to be multi-layer switch.

0:06:02.980000 --> 0:06:04.460000
 Don't have to do this.

0:06:04.460000 --> 0:06:09.840000
 It just makes it so that when I'm looking
 at it in the topology, it looks

0:06:09.840000 --> 0:06:11.440000
 a little bit better.

0:06:11.440000 --> 0:06:13.900000
 So I actually know what I'm
 looking at right here.

0:06:13.900000 --> 0:06:16.280000
 Now you can't change the name.

0:06:16.280000 --> 0:06:18.480000
 It still has to represent
 as cloud.

0:06:18.480000 --> 0:06:22.100000
 Right now it's saying cloud two because
 I already created a cloud to test

0:06:22.100000 --> 0:06:24.220000
 this out before I did the video.

0:06:24.220000 --> 0:06:27.600000
 But if this is your first cloud,
 you'll probably say cloud one.

0:06:27.600000 --> 0:06:29.420000
 All right. So now I'm
 done with that.

0:06:29.420000 --> 0:06:32.260000
 Go ahead and go on my
 router and start it.

0:06:32.260000 --> 0:06:38.160000
 Now one thing you'll notice and the
 switch might talk about this.

0:06:38.160000 --> 0:06:40.200000
 Now my particular case, it's not.

0:06:40.200000 --> 0:06:45.080000
 But when I did this the first time, you
 can see I was getting duplex mismatch

0:06:45.080000 --> 0:06:51.840000
 messages. And that's because by default,
 the router's interface is connecting

0:06:51.840000 --> 0:06:54.420000
 into the cloud is running
 half duplex.

0:06:54.420000 --> 0:06:56.600000
 And the switch was saying,
 hey, I'm confused.

0:06:56.600000 --> 0:06:58.020000
 I'm running full duplex.

0:06:58.020000 --> 0:07:01.740000
 The thing I'm connected to is half duplex,
 but we can fix that real easily.

0:07:01.740000 --> 0:07:03.980000
 So let's just double
 click on the router.

0:07:03.980000 --> 0:07:06.200000
 And now we're in that router here.


0:07:06.200000 --> 0:07:10.420000
 So we just go into the
 router's interface.

0:07:10.420000 --> 0:07:15.440000
 And whenever you change things at the
 physical or the data link layer,

0:07:15.440000 --> 0:07:18.780000
 I always recommend that you shut
 down the interface first.

0:07:18.780000 --> 0:07:22.160000
 You can just have unpredictable results
 if you try to change physical

0:07:22.160000 --> 0:07:27.740000
 or data link layer actually
 up and running.

0:07:27.740000 --> 0:07:29.540000
 So I'm going to shut it down.

0:07:29.540000 --> 0:07:32.960000
 And now I'm going to change
 the duplex to full.

0:07:32.960000 --> 0:07:36.860000
 I'll do a no shut.

0:07:36.860000 --> 0:07:46.020000
 Okay. And now how do I know
 it's actually connected?

0:07:46.020000 --> 0:07:47.460000
 Well, there's a couple of ways.

0:07:47.460000 --> 0:07:53.080000
 One way you can do is because my switch
 is doing CDP, I can just do show

0:07:53.080000 --> 0:07:57.700000
 CDP neighbor on my virtual
 or my emulated router.

0:07:57.700000 --> 0:08:01.680000
 And you can see right here, it's
 connected to keys switch.

0:08:01.680000 --> 0:08:05.300000
 Another way I can tell this
 is on my actual switch.

0:08:05.300000 --> 0:08:06.440000
 Now I connected it physically.

0:08:06.440000 --> 0:08:09.580000
 Let's go back to my
 drawing right here.

0:08:09.580000 --> 0:08:13.500000
 I connected it physically
 to port zero slash two.

0:08:13.500000 --> 0:08:19.100000
 That's the port that I'm actually
 connected to on the switch.

0:08:19.100000 --> 0:08:23.080000
 And on the switch, show run interface
 fast ethernet zero slash two.

0:08:23.080000 --> 0:08:26.700000
 You can see I've just simply configured
 it as an access port and it's

0:08:26.700000 --> 0:08:28.900000
 defaulting to VLAN one.

0:08:28.900000 --> 0:08:33.800000
 And then what I also did is under my
 VLAN one under my switched virtual

0:08:33.800000 --> 0:08:37.040000
 interface, I gave an IP address.

0:08:37.040000 --> 0:08:39.160000
 And then my router here.

0:08:39.160000 --> 0:08:42.900000
 Now, still getting
 a duplex mismatch.

0:08:42.900000 --> 0:08:45.820000
 Let's take a look
 at our interface.

0:08:45.820000 --> 0:08:48.060000
 Fast ethernet zero slash zero.

0:08:48.060000 --> 0:08:52.040000
 This might just be an old message.


0:08:52.040000 --> 0:08:53.120000
 Let's take a look here.

0:08:53.120000 --> 0:08:57.920000
 Show interface fast ethernet
 zero slash two.

0:08:57.920000 --> 0:09:04.820000
 And right now this
 guy is full duplex.

0:09:04.820000 --> 0:09:06.340000
 So we should have parity here.

0:09:06.340000 --> 0:09:08.280000
 We should have full duplex
 on both sides.

0:09:08.280000 --> 0:09:10.280000
 I'm going to ignore that
 message for the moment.

0:09:10.280000 --> 0:09:15.060000
 So on the router side, you can see,
 let's go ahead and configure an IP

0:09:15.060000 --> 0:09:17.200000
 address on that router's
 interface.

0:09:17.200000 --> 0:09:20.160000
 This is just going to give further
 proof that I am really connected to

0:09:20.160000 --> 0:09:21.540000
 that external device.

0:09:21.540000 --> 0:09:25.880000
 IP address one dot one dot one dot
 two, because my switch was one dot

0:09:25.880000 --> 0:09:27.300000
 one dot one dot one.

0:09:27.300000 --> 0:09:30.880000
 Guess I have to go in the interface
 first to do that.

0:09:30.880000 --> 0:09:37.240000
 Okay, so if I'm really connected to
 that physical switch, I should be

0:09:37.240000 --> 0:09:38.420000
 able to ping it.

0:09:38.420000 --> 0:09:42.180000
 And it's going to ARP.

0:09:42.180000 --> 0:09:44.280000
 And then I have a successful ping.


0:09:44.280000 --> 0:09:51.820000
 So that's it. So to recap everything we
 did, step number one was to actually

0:09:51.820000 --> 0:09:55.980000
 go to my physical device, turn it on, configure
 it, however, want to configure

0:09:55.980000 --> 0:09:59.900000
 it, and then connect a physical ethernet
 cable from one of the interfaces

0:09:59.900000 --> 0:10:05.720000
 on my physical device into the ethernet
 net card on my laptop where I'm

0:10:05.720000 --> 0:10:07.360000
 running GNS three.

0:10:07.360000 --> 0:10:10.260000
 So that completed the physical
 configuration.

0:10:10.260000 --> 0:10:12.680000
 Step number two was I
 started up GNS three.

0:10:12.680000 --> 0:10:15.400000
 I created my topology,
 however I wanted.

0:10:15.400000 --> 0:10:19.320000
 And then the key component to connect
 these two together was to use the

0:10:19.320000 --> 0:10:24.820000
 cloud node. And so within the cloud
 node, I just right clicked on it.

0:10:24.820000 --> 0:10:26.500000
 I selected configure.

0:10:26.500000 --> 0:10:31.800000
 And under the ethernet tab right here,
 I ensured that this drop down box

0:10:31.800000 --> 0:10:37.160000
 was selecting my local area connection,
 which is my LAN adapter.

0:10:37.160000 --> 0:10:39.680000
 Now I don't want two of them.

0:10:39.680000 --> 0:10:45.120000
 I'm not going to worry
 about that for now.

0:10:45.120000 --> 0:10:48.180000
 Once I had that selected, then the last
 piece of the puzzle was to start

0:10:48.180000 --> 0:10:52.020000
 up my router in this particular
 case, add a link.

0:10:52.020000 --> 0:10:53.840000
 Actually, you should do this
 before you start the router.

0:10:53.840000 --> 0:10:56.580000
 While the router was still powered
 off, add a link between it and the

0:10:56.580000 --> 0:11:02.080000
 cloud. Optionally, you can change the
 icon of the cloud and then you start

0:11:02.080000 --> 0:11:05.360000
 up your router. Now, before I finish,
 one last thing I want to talk about,

0:11:05.360000 --> 0:11:09.900000
 I mentioned that the cloud and
 the host are interchangeable.

0:11:09.900000 --> 0:11:13.120000
 Let me just drag the host
 in here for just a second.

0:11:13.120000 --> 0:11:19.220000
 Now if I right click on host, you'll
 see that it also has the option to

0:11:19.220000 --> 0:11:21.300000
 connect to various things here.

0:11:21.300000 --> 0:11:22.800000
 It's really no different.

0:11:22.800000 --> 0:11:25.000000
 The configuration is
 exactly the same.

0:11:25.000000 --> 0:11:27.980000
 So why would I use
 one over the other?

0:11:27.980000 --> 0:11:31.400000
 Well, let's say that here in my actual
 lab, right next to me, I had, let's

0:11:31.400000 --> 0:11:33.560000
 say, three physical switches.

0:11:33.560000 --> 0:11:36.640000
 You know, I want to test out some things
 like multiple spanning trees

0:11:36.640000 --> 0:11:40.180000
 and VLAN access lists and
 private VLANs and stuff.

0:11:40.180000 --> 0:11:43.280000
 And I sort of figure that I need a
 minimum of three physical switches

0:11:43.280000 --> 0:11:44.720000
 to do all that stuff.

0:11:44.720000 --> 0:11:48.060000
 In that particular case, it would be
 appropriate for me to use the cloud

0:11:48.060000 --> 0:11:53.140000
 icon because my simulated environment is
 connecting to a real world environment

0:11:53.140000 --> 0:11:56.900000
 of more than one thing,
 multiple devices.

0:11:56.900000 --> 0:12:02.100000
 Now on the flip side, let's say I really
 was just going to connect to,

0:12:02.100000 --> 0:12:03.700000
 let's say, a AAA server.

0:12:03.700000 --> 0:12:07.320000
 Let's say I had a physical server sitting
 on the desk next to me that

0:12:07.320000 --> 0:12:13.560000
 was running Windows 2000 or Windows R8
 or whatever, and it had a AAA radius

0:12:13.560000 --> 0:12:15.960000
 server inside of it that
 I had up and running.

0:12:15.960000 --> 0:12:18.040000
 And then I was going
 to connect to that.

0:12:18.040000 --> 0:12:21.560000
 Well, I could still use the cloud node,
 but it might be more appropriate

0:12:21.560000 --> 0:12:25.980000
 in that particular case to instead
 use the host node because really I

0:12:25.980000 --> 0:12:28.880000
 am connecting to a host, a server.


0:12:28.880000 --> 0:12:30.640000
 Really is completely up to you.

0:12:30.640000 --> 0:12:33.240000
 They both do exactly
 the same thing.

0:12:33.240000 --> 0:12:36.640000
 So that concludes this particular video
 on how to connect your GNS3 virtual

0:12:36.640000 --> 0:12:39.180000
 environment to a physical device.

