WEBVTT

0:00:08.040000 --> 0:00:11.640000
 So at this point, you should hopefully
 feel pretty comfortable with adding

0:00:11.640000 --> 0:00:16.040000
 routers and switches and frame relay
 switches into your topology, into

0:00:16.040000 --> 0:00:17.680000
 your GNS3 network.

0:00:17.680000 --> 0:00:19.960000
 So you might be getting to the point
 where you say, you know what, I'd

0:00:19.960000 --> 0:00:22.400000
 really like to add a
 host into my network.

0:00:22.400000 --> 0:00:25.420000
 I'd like to have a host for a variety
 of reasons, maybe to ping back and

0:00:25.420000 --> 0:00:27.940000
 forth or to do some other
 types of testing.

0:00:27.940000 --> 0:00:29.720000
 Now let's step back for
 here for a second.

0:00:29.720000 --> 0:00:32.300000
 You might wonder, well, Keith,
 why do I need a host?

0:00:32.300000 --> 0:00:36.860000
 I mean, if I just want to do ping tests
 or if I want to generate some

0:00:36.860000 --> 0:00:41.260000
 just test access lists or something like
 that, can I just plug in another

0:00:41.260000 --> 0:00:43.260000
 router and ping from the router?

0:00:43.260000 --> 0:00:45.860000
 Well, certainly you can do that,
 but keep in mind one thing.

0:00:45.860000 --> 0:00:49.820000
 Anytime you plug a router into your topology
 and then you start it, you're

0:00:49.820000 --> 0:00:52.520000
 consuming another instance
 of router memory.

0:00:52.520000 --> 0:00:57.900000
 If that software image that router is
 running takes 512 megabits per second,

0:00:57.900000 --> 0:01:01.760000
 let's say it's a 7200 series router,
 now you're just eating up a lot more

0:01:01.760000 --> 0:01:06.840000
 RAM and your laptop simply to have
 some device that you can ping from.

0:01:06.840000 --> 0:01:10.400000
 So for here, for something like that
 and a lot of other useful reasons,

0:01:10.400000 --> 0:01:15.900000
 I'd like to talk about the VPCS, the
 virtual PC simulator that's included

0:01:15.900000 --> 0:01:20.060000
 as yet another built
-in node within GNS3.

0:01:20.060000 --> 0:01:23.500000
 Now, I've been using this quite a bit
 throughout the various topologies

0:01:23.500000 --> 0:01:26.540000
 and I've been promising you, well,
 I'll get to it, I'll get to it.

0:01:26.540000 --> 0:01:29.600000
 Well, now is our time to talk about it,
 so let's talk about a little bit.

0:01:29.600000 --> 0:01:35.360000
 So first of all, this particular node
 is available right here in the Browse

0:01:35.360000 --> 0:01:37.760000
 End Devices section.

0:01:37.760000 --> 0:01:39.360000
 So that's where you
 would find this.

0:01:39.360000 --> 0:01:45.300000
 So click on that and then we're
 going to be using VPCS.

0:01:45.300000 --> 0:01:47.940000
 So you just drag and drop it on
 just like you normally would.

0:01:47.940000 --> 0:01:53.200000
 Now these, unlike your built-in ethernet
 switches and your built-in frame

0:01:53.200000 --> 0:01:57.600000
 relay switch and everything, these you
 can turn on and turn off and notice

0:01:57.600000 --> 0:02:01.340000
 that by default is deactivated,
 it's turned off.

0:02:01.340000 --> 0:02:04.680000
 So let me get rid
 of this one here.

0:02:04.680000 --> 0:02:09.260000
 So I've already got three instances
 of my virtual PCs in this particular

0:02:09.260000 --> 0:02:13.380000
 topology and I want to show you some
 of the real power behind this.

0:02:13.380000 --> 0:02:16.960000
 For example, let's start out
 with PC number two here.

0:02:16.960000 --> 0:02:20.700000
 And in this particular PC, I just want
 to give it a static IP address

0:02:20.700000 --> 0:02:23.700000
 and mask and a static
 default gateway.

0:02:23.700000 --> 0:02:25.020000
 Real easy to do that.

0:02:25.020000 --> 0:02:28.320000
 So just go ahead and double click on
 it to open it up and this is what

0:02:28.320000 --> 0:02:29.900000
 your console window
 will look like.

0:02:29.900000 --> 0:02:33.220000
 It actually has a pretty intuitive
 help menu and I like it a lot.

0:02:33.220000 --> 0:02:37.160000
 Just type, for example, the question mark
 and you can see all the different

0:02:37.160000 --> 0:02:39.140000
 options are available to you here.


0:02:39.140000 --> 0:02:42.980000
 So in my particular case, I say, well,
 I want to add a static IP address.

0:02:42.980000 --> 0:02:46.300000
 Well, we can see from here that IP
 is probably what I want to do.

0:02:46.300000 --> 0:02:48.300000
 IP what? What should I do?

0:02:48.300000 --> 0:02:50.240000
 IP and you can see it actually
 gives you an example.

0:02:50.240000 --> 0:02:55.520000
 IP, the address, the mask and
 then the default gateway.

0:02:55.520000 --> 0:03:00.200000
 So in my particular case, if I want
 this guy to be 4441, I would just

0:03:00.200000 --> 0:03:08.160000
 type IP, 4.4.1 slash 24 and then
 as default gateway is 4.4.4.2.

0:03:08.160000 --> 0:03:11.360000
 So you can see it's a little bit of
 a different syntax than typing an

0:03:11.360000 --> 0:03:16.020000
 IP address on a router's interface
 where you actually type IP address.

0:03:16.020000 --> 0:03:18.040000
 Here you just type,
 as you can see.

0:03:18.040000 --> 0:03:22.960000
 Now there's one, before I go any further
 with VPCS, one very important

0:03:22.960000 --> 0:03:24.640000
 thing you have to remember.

0:03:24.640000 --> 0:03:26.760000
 Let's think about routers
 for a second.

0:03:26.760000 --> 0:03:30.160000
 If you make a change in your router's
 configuration, you're making a change

0:03:30.160000 --> 0:03:32.880000
 in the running configuration,
 right?

0:03:32.880000 --> 0:03:37.040000
 So what happens if you stop that router
 and you haven't saved those configs

0:03:37.040000 --> 0:03:39.880000
 or you completely
 stop your project?

0:03:39.880000 --> 0:03:43.620000
 Anything in your running config
 that has not been saved is gone.

0:03:43.620000 --> 0:03:47.280000
 It's wiped out. So that's why as hopefully
 by this point in time you know,

0:03:47.280000 --> 0:03:50.600000
 with routers you should always issue
 the right memory command or the copy

0:03:50.600000 --> 0:03:53.580000
 run start command after
 you make changes.

0:03:53.580000 --> 0:03:57.660000
 Well in a similar way, these virtual
 PCs, when you make a change to their

0:03:57.660000 --> 0:04:01.300000
 configuration like I just did
 here, you have to save it.

0:04:01.300000 --> 0:04:05.580000
 If you don't, the moment you turn off
 that virtual PC or the moment you

0:04:05.580000 --> 0:04:10.640000
 exit from your GNS3 project, whatever
 you configured your virtual PC for,

0:04:10.640000 --> 0:04:12.220000
 his settings will be gone.

0:04:12.220000 --> 0:04:14.960000
 It'll vanish. So how do
 we save his settings?

0:04:14.960000 --> 0:04:18.120000
 It's simply the save command.

0:04:18.120000 --> 0:04:19.180000
 And that's all you have to do.

0:04:19.180000 --> 0:04:23.020000
 So remember that with your virtual PC
 to issue the save command whenever

0:04:23.020000 --> 0:04:24.420000
 you make a change.

0:04:24.420000 --> 0:04:27.880000
 So that's what, that's a way of configuring
 a static IP address, mask

0:04:27.880000 --> 0:04:29.340000
 and default gateway.

0:04:29.340000 --> 0:04:31.300000
 What about over here?

0:04:31.300000 --> 0:04:35.320000
 PC number one. I want to configure
 him as a DHCP client.

0:04:35.320000 --> 0:04:39.600000
 Well this is another powerful thing
 we can do here within VPCS.

0:04:39.600000 --> 0:04:41.800000
 So I'll just double click on him.

0:04:41.800000 --> 0:04:45.240000
 So I'm on PC one.

0:04:45.240000 --> 0:04:52.040000
 And now if I do IP question
 mark, I can just do IP DHCP.

0:04:52.040000 --> 0:04:53.840000
 That's all I have to do.

0:04:53.840000 --> 0:04:56.820000
 Now there are some options
 if you wish.

0:04:56.820000 --> 0:05:02.600000
 But if you just do IP DHCP, the moment
 you type that, it will send out

0:05:02.600000 --> 0:05:07.520000
 a DHCP discover message and attempt
 to get an IP address.

0:05:07.520000 --> 0:05:11.600000
 Now this guy already has an IP
 address as you can see 1114.

0:05:11.600000 --> 0:05:13.740000
 So let's see actually how
 this works in action.

0:05:13.740000 --> 0:05:17.360000
 So number one, let's try releasing
 that address and getting a new one.

0:05:17.360000 --> 0:05:24.180000
 So IP DHCP and it says right here, minus
 R, actually minus X is to release

0:05:24.180000 --> 0:05:26.380000
 the address. So minus X.

0:05:26.380000 --> 0:05:30.100000
 Show IP. Okay, so now we
 have nothing, right?

0:05:30.100000 --> 0:05:32.960000
 So minus X was to release the
 address and now it's gone.

0:05:32.960000 --> 0:05:38.540000
 Still remember the DNS settings and
 the DHCP server but the address is

0:05:38.540000 --> 0:05:40.140000
 gone. So how do I get a new one?

0:05:40.140000 --> 0:05:45.680000
 Just IP DHCP. I'll explain to you in
 just a moment what these letters

0:05:45.680000 --> 0:05:48.820000
 mean. And there we go.

0:05:48.820000 --> 0:05:51.300000
 So what did those letters mean
 that I was looking at?

0:05:51.300000 --> 0:05:56.000000
 This is actually showing
 you the DHCP decode.

0:05:56.000000 --> 0:06:01.340000
 This is the discover and then he sent
 another discover and then he received

0:06:01.340000 --> 0:06:07.420000
 a DHCP offer. Then the client sent out
 a DHCP request and the transaction

0:06:07.420000 --> 0:06:11.900000
 was finished by receiving
 a DHCP acknowledgement.

0:06:11.900000 --> 0:06:14.740000
 And what's kind of nice is you can
 drill down even further than that.

0:06:14.740000 --> 0:06:20.800000
 If I do IP DHCP question mark, you'll
 see I can also do minus D to actually

0:06:20.800000 --> 0:06:22.200000
 get a packet decode.

0:06:22.200000 --> 0:06:23.120000
 So let's try that.

0:06:23.120000 --> 0:06:28.200000
 IP DHCP, I want to release
 my address and minus D.

0:06:28.200000 --> 0:06:30.140000
 I want to see the decode of it.

0:06:30.140000 --> 0:06:30.860000
 And there we go.

0:06:30.860000 --> 0:06:36.700000
 See? So he sent out a DHCP option
 53 which is a release message.

0:06:36.700000 --> 0:06:41.320000
 And now I can do IP DHCP minus D to
 actually watch the whole process in

0:06:41.320000 --> 0:06:46.200000
 action. So now he's sending
 out requests.

0:06:46.200000 --> 0:06:47.760000
 There's the reply.

0:06:47.760000 --> 0:06:49.300000
 And then we're done.

0:06:49.300000 --> 0:06:53.900000
 So let's go up to the top here.

0:06:53.900000 --> 0:06:58.760000
 Okay so the first message
 was a DHCP discover.

0:06:58.760000 --> 0:07:02.640000
 Then he sent out another discover.


0:07:02.640000 --> 0:07:05.640000
 And then we received back the offer
 and we can see all the information

0:07:05.640000 --> 0:07:08.360000
 that was included in that offer.

0:07:08.360000 --> 0:07:12.620000
 Then we sent out a DHCP request and
 the final step in the process was

0:07:12.620000 --> 0:07:17.020000
 a DHCP server sent back to
 us a DHCP acknowledgement.

0:07:17.020000 --> 0:07:21.300000
 So the minus D option is very useful
 in this particular case as far as

0:07:21.300000 --> 0:07:25.540000
 DHCP is concerned if you want to actually
 watch the DHCP transaction.

0:07:25.540000 --> 0:07:29.600000
 Now you might be wondering, well wait
 a second Keith, who's the DHCP server

0:07:29.600000 --> 0:07:31.520000
 in this particular topology?

0:07:31.520000 --> 0:07:35.840000
 Well, as you go through your CCNA studies,
 one of the things they're going

0:07:35.840000 --> 0:07:40.460000
 to expect you to know is how to configure
 a router as a DHCP server.

0:07:40.460000 --> 0:07:42.400000
 I'm not going to go into the
 details of that right now.

0:07:42.400000 --> 0:07:45.320000
 I will show you that I've
 done that on router two.

0:07:45.320000 --> 0:07:54.040000
 If I show you his configuration right
 up here towards the top is the DHCP

0:07:54.040000 --> 0:07:58.920000
 configuration configuring this particular
 router as the DHCP server.

0:07:58.920000 --> 0:08:01.480000
 So that was already pre-done.

0:08:01.480000 --> 0:08:04.540000
 Let's get back to VPCS
 here for a moment.

0:08:04.540000 --> 0:08:08.500000
 So another powerful tool VPCS,
 you can ping from it.

0:08:08.500000 --> 0:08:14.600000
 For example, I can ping from PC1 to
 PC3 to see if my routing and frame

0:08:14.600000 --> 0:08:15.860000
 relay and everything is set up.

0:08:15.860000 --> 0:08:21.000000
 So let's see if PC1 can ping 551.

0:08:21.000000 --> 0:08:23.500000
 Let's see if it works.

0:08:23.500000 --> 0:08:34.140000
 We're getting a timeout and
 then the ping is successful.

0:08:34.140000 --> 0:08:36.740000
 I might be thinking, OK,
 Keith, but big deal.

0:08:36.740000 --> 0:08:38.640000
 I mean, I could ping
 from a router.

0:08:38.640000 --> 0:08:41.320000
 Why use this virtual PC?

0:08:41.320000 --> 0:08:45.800000
 Well, the virtual PC for one thing
 uses a lot less memory than another

0:08:45.800000 --> 0:08:47.220000
 router instance does.

0:08:47.220000 --> 0:08:50.920000
 So yes, you could have put a router into
 your topology and had that router

0:08:50.920000 --> 0:08:54.940000
 set up as a DHCP client and
 watched a DHCP transaction.

0:08:54.940000 --> 0:08:56.120000
 Sure, you could have done that.

0:08:56.120000 --> 0:08:59.700000
 Sure, you could ping from a router
 and watch that and test your access

0:08:59.700000 --> 0:09:03.880000
 list and stuff. But remember that router
 is using up a lot more memory

0:09:03.880000 --> 0:09:07.140000
 in your laptop than VPCS is.

0:09:07.140000 --> 0:09:11.000000
 And there's things you can do from
 here within VPCS that you can't do

0:09:11.000000 --> 0:09:12.080000
 within a router.

0:09:12.080000 --> 0:09:16.580000
 For example, let's look what happens
 if I type ping question mark.

0:09:16.580000 --> 0:09:19.120000
 I can do UDP pings.

0:09:19.120000 --> 0:09:21.520000
 I can do TCP pings.

0:09:21.520000 --> 0:09:25.960000
 I can set any, if I'm doing a TCP ping,
 I can set any of the flags within

0:09:25.960000 --> 0:09:29.880000
 the TCP header. What if I'm testing quality
 of service and I need to have

0:09:29.880000 --> 0:09:31.000000
 a packet generator?

0:09:31.000000 --> 0:09:35.960000
 I want to see if my quality of service
 police or markers or stuff are

0:09:35.960000 --> 0:09:37.120000
 working correctly.

0:09:37.120000 --> 0:09:41.020000
 Well, how would you create a packet
 generator out of a Cisco router?

0:09:41.020000 --> 0:09:42.520000
 It'd be kind of hard to do.

0:09:42.520000 --> 0:09:44.040000
 A ping's not going to do it.

0:09:44.040000 --> 0:09:50.660000
 But here with VPCS, I could ping via UDP
 and do it like every five seconds.

0:09:50.660000 --> 0:09:55.200000
 And then I could use the minus T
 option to say, just keep going.

0:09:55.200000 --> 0:10:01.320000
 For example, ping, who do
 I want to ping, 555 one?

0:10:01.320000 --> 0:10:06.480000
 I want to do minus two because
 I want to be in UDP mode.

0:10:06.480000 --> 0:10:11.360000
 And then I want to do minus I and I'll
 have those pings go out every 10

0:10:11.360000 --> 0:10:15.060000
 milliseconds. That's minus I.

0:10:15.060000 --> 0:10:17.440000
 And then I'm going to do minus T.

0:10:17.440000 --> 0:10:21.040000
 Keep those pings going
 until I stop them.

0:10:21.040000 --> 0:10:23.560000
 And there they go.

0:10:23.560000 --> 0:10:25.400000
 Now, let's keep running
 with them for a moment.

0:10:25.400000 --> 0:10:26.820000
 Let's keep letting them go.

0:10:26.820000 --> 0:10:32.120000
 Now, if I go over my router router 2
 on router 2, let's go ahead and check

0:10:32.120000 --> 0:10:34.680000
 out those pings are going
 through him right now.

0:10:34.680000 --> 0:10:38.100000
 And they should be coming in fast,
 even at 0, 0 and going out, serial

0:10:38.100000 --> 0:10:42.660000
 2 slash 0. So if I had some sort of
 police or something else like that

0:10:42.660000 --> 0:10:46.560000
 configured for quality of service, maybe
 I applied it to serial 2 slash

0:10:46.560000 --> 0:10:50.800000
 0. Let's see what the actual output rate
 is right now considering massive

0:10:50.800000 --> 0:10:54.880000
 UDP pings are leaving
 on that interface.

0:10:54.880000 --> 0:10:56.560000
 All right. So let's
 go to router 2.

0:10:56.560000 --> 0:10:59.300000
 Show interface serial 2 slash 0.

0:10:59.300000 --> 0:11:06.960000
 We can see that right now the output
 rate is about 16,000 bits per second.

0:11:06.960000 --> 0:11:09.740000
 Now I tried this before
 I did this recording.

0:11:09.740000 --> 0:11:15.820000
 And if you wait, oh, about five or six
 minutes, this will get up not too

0:11:15.820000 --> 0:11:19.480000
 far. It'll go, I waited for about three
 or four minutes and it got up

0:11:19.480000 --> 0:11:22.220000
 to about 64,000 bits per second.

0:11:22.220000 --> 0:11:25.820000
 But as far as just QOS testing
 is concerned, that's fine.

0:11:25.820000 --> 0:11:28.820000
 All right. If you just want to create
 a simple police and try to police

0:11:28.820000 --> 0:11:33.040000
 this down to three kilobits per second
 or eight kilobits per second, you

0:11:33.040000 --> 0:11:36.740000
 could do that. But in order to test a
 police, you have to have some traffic

0:11:36.740000 --> 0:11:38.740000
 coming in to police it.

0:11:38.740000 --> 0:11:42.780000
 So this VPCS can be used to generate
 that traffic, but we're not done

0:11:42.780000 --> 0:11:50.880000
 yet. So let me go back to my VPCS
 control C breakout of it.

0:11:50.880000 --> 0:11:54.820000
 For you aspiring CCNA candidates, you're
 going to be learning about Cisco

0:11:54.820000 --> 0:11:57.800000
 access lists. How do you
 test your access list?

0:11:57.800000 --> 0:12:01.940000
 Well, certainly you can create simple
 access lists like blocking telnet

0:12:01.940000 --> 0:12:06.020000
 or blocking ping because telnet and
 ping traffic is stuff you can source

0:12:06.020000 --> 0:12:07.320000
 from a router, right?

0:12:07.320000 --> 0:12:10.540000
 You can jump onto a router and from
 that router, you can type ping or

0:12:10.540000 --> 0:12:13.160000
 telnet and then see if
 your access list works.

0:12:13.160000 --> 0:12:16.480000
 But what if you want to create some
 more complex access lists that are

0:12:16.480000 --> 0:12:21.300000
 maybe blocking or permitting certain
 TCP ports or UDP ports?

0:12:21.300000 --> 0:12:24.800000
 In that case, how would you generate
 the traffic to actually test that

0:12:24.800000 --> 0:12:31.120000
 access list? You could do it from right
 here within VPCS as an example.

0:12:31.120000 --> 0:12:35.880000
 On router four here, I have created an
 outbound access list on fast ethernet

0:12:35.880000 --> 0:12:41.460000
 00. And that outbound access list is
 permitting all traffic except UDP

0:12:41.460000 --> 0:12:46.140000
 traffic going to port number
 99 as a destination.

0:12:46.140000 --> 0:12:53.280000
 Show run. So you can see here, I've
 applied the access list as an access

0:12:53.280000 --> 0:13:05.980000
 group outbound. And if I go down access
 list 101, here is that access

0:13:05.980000 --> 0:13:11.120000
 list. That works if the destination UDP
 port number is 99 and then permitting

0:13:11.120000 --> 0:13:12.440000
 everything else.

0:13:12.440000 --> 0:13:14.360000
 So how would I test that?

0:13:14.360000 --> 0:13:17.820000
 Well, let's go back to my VPCS.

0:13:17.820000 --> 0:13:20.560000
 So ping, question mark.

0:13:20.560000 --> 0:13:25.540000
 All right, so why don't we do ping
 555-1, that's the remote PC.

0:13:25.540000 --> 0:13:29.380000
 And why don't we do
 minus two for UDP?

0:13:29.380000 --> 0:13:31.240000
 And then let's do minus P.

0:13:31.240000 --> 0:13:34.620000
 And notice it's a lower case P here,
 very important that you select the

0:13:34.620000 --> 0:13:39.720000
 lower case P for the port number as opposed
 to the upper case P for protocol,

0:13:39.720000 --> 0:13:42.440000
 which is the IP protocol
 in the IP header.

0:13:42.440000 --> 0:13:44.920000
 So I'm going to do minus P.

0:13:44.920000 --> 0:13:47.760000
 And let's start out with a port
 number that should be OK.

0:13:47.760000 --> 0:13:53.440000
 The access list should allow UDP pings
 going to destination port 90.

0:13:53.440000 --> 0:13:56.180000
 Might get a timeout for one or two
 of them, but then they should work.

0:13:56.180000 --> 0:13:57.840000
 There we go. So now
 they're working.

0:13:57.840000 --> 0:13:59.780000
 Now let's test to see if
 the access list works.

0:13:59.780000 --> 0:14:02.580000
 Let's change that destination
 port number to 99.

0:14:02.580000 --> 0:14:05.520000
 The access list is supposed
 to drop that.

0:14:05.520000 --> 0:14:10.600000
 And it is. We're getting communication
 administratively prohibited.

0:14:10.600000 --> 0:14:14.320000
 So this is a great way to also
 test your access list.

0:14:14.320000 --> 0:14:16.800000
 There's a lot of other things
 that can do here as well.

0:14:16.800000 --> 0:14:19.240000
 One other thing I want to show
 you, which is really neat.

0:14:19.240000 --> 0:14:25.940000
 If you just do set question mark, you'll
 see that one of the options is

0:14:25.940000 --> 0:14:28.980000
 the set dump option.

0:14:28.980000 --> 0:14:34.560000
 So you can do set dump all.

0:14:34.560000 --> 0:14:41.420000
 And what this does, it's actually like
 doing a debug packet all on a router.

0:14:41.420000 --> 0:14:45.080000
 This basically says now any packet
 that this PC sends out, whether it

0:14:45.080000 --> 0:14:49.900000
 be a UDP ping, a TCP ping, whatever,
 I want to see all of it.

0:14:49.900000 --> 0:14:53.540000
 So for example, let's do that
 same UDP ping I just did.

0:14:53.540000 --> 0:14:58.240000
 See, now we get a lot more
 information about it.

0:14:58.240000 --> 0:15:04.460000
 We see the 3332, so that's the actual
 address of the router that has the

0:15:04.460000 --> 0:15:05.880000
 access list on it.

0:15:05.880000 --> 0:15:07.660000
 We see the time to live.

0:15:07.660000 --> 0:15:08.920000
 We see milliseconds.

0:15:08.920000 --> 0:15:10.920000
 We see the ICMP type code.

0:15:10.920000 --> 0:15:13.040000
 Okay, this isn't that
 big of a deal.

0:15:13.040000 --> 0:15:14.540000
 But look at the real
 power of this.

0:15:14.540000 --> 0:15:16.780000
 What if I want to test out TCP?

0:15:16.780000 --> 0:15:19.480000
 Maybe you've just learned about TCP and
 you want to see, okay, I've learned

0:15:19.480000 --> 0:15:21.620000
 there's this TCP three
-way handshake.

0:15:21.620000 --> 0:15:24.380000
 I've learned a little bit
 about the TCP flags.

0:15:24.380000 --> 0:15:26.800000
 So I want to see some of
 that stuff in action.

0:15:26.800000 --> 0:15:28.900000
 Well, we can do this.

0:15:28.900000 --> 0:15:31.240000
 PING question mark.

0:15:31.240000 --> 0:15:33.940000
 Let's do PING 5551.

0:15:33.940000 --> 0:15:38.840000
 And remember, we still have these
 set dump all configured, right?

0:15:38.840000 --> 0:15:40.960000
 That didn't stop right there.

0:15:40.960000 --> 0:15:46.360000
 Set dump all. It's sort of like a
 debug all in the world of VPCS.

0:15:46.360000 --> 0:15:49.160000
 So we'll do PING 5551.

0:15:49.160000 --> 0:15:53.220000
 Let's do minus three for TCP mode.


0:15:53.220000 --> 0:15:55.120000
 And why don't we do a...

0:15:55.120000 --> 0:15:57.160000
 That's it. We'll just do that.

0:15:57.160000 --> 0:16:00.520000
 TCP PINGS to 5551.

0:16:00.520000 --> 0:16:10.820000
 Okay, so something
 is blocking this.

0:16:10.820000 --> 0:16:13.580000
 Can we PING 5551?

0:16:13.580000 --> 0:16:15.600000
 Now we can still PING it.

0:16:15.600000 --> 0:16:20.320000
 We just can't do a TCP PING.

0:16:20.320000 --> 0:16:25.860000
 Sequence two, 5551, minus three, minus
 three is supposed to be TCP mode,

0:16:25.860000 --> 0:16:31.900000
 all right? Well, let's go over to our
 routers real quickly and troubleshoot

0:16:31.900000 --> 0:16:36.280000
 this. First of all, let me look at
 my access list on router four.

0:16:36.280000 --> 0:16:41.120000
 So I'm denying UDP.

0:16:41.120000 --> 0:16:43.660000
 I'm permitting all other IP.

0:16:43.660000 --> 0:16:45.580000
 So that should be all right, okay?


0:16:45.580000 --> 0:16:51.800000
 Let's now go over to the
 remote PC of 5551.

0:16:51.800000 --> 0:16:56.700000
 And let's verify that he actually
 has an IP address.

0:16:56.700000 --> 0:17:00.720000
 And he is 5551 and his default
 gateway is 5552.

0:17:00.720000 --> 0:17:03.200000
 All right, that looks good.

0:17:03.200000 --> 0:17:06.960000
 So there's no reason I can
 think of it at this point.

0:17:06.960000 --> 0:17:10.560000
 Why those TCP PINGS
 were not functional.

0:17:10.560000 --> 0:17:12.160000
 Let's set the dump to off.

0:17:12.160000 --> 0:17:16.900000
 Set dump off. That's sort of like an
 undibug all in the world of Cisco

0:17:16.900000 --> 0:17:29.520000
 terminology. PING 5551, okay, well,
 minus three should be TCP mode.

0:17:29.520000 --> 0:17:33.100000
 And just like a Cisco router, you can
 use the up and down arrows on your

0:17:33.100000 --> 0:17:39.180000
 keyboard because it does keep a command
 history of what you've done.

0:17:39.180000 --> 0:17:48.540000
 PING 5551 minus three and we'll
 do a count of three of them.

0:17:48.540000 --> 0:17:50.300000
 Okay, so that's working.

0:17:50.300000 --> 0:17:52.160000
 All right, so now let's turn
 the set dump back on.

0:17:52.160000 --> 0:18:08.540000
 Set dump all. And let's
 do that PING again.

0:18:08.540000 --> 0:18:15.840000
 Okay, well, set dump
 question mark.

0:18:15.840000 --> 0:18:19.240000
 Ah, it's set dump detail.

0:18:19.240000 --> 0:18:20.240000
 That's what we're looking for.

0:18:20.240000 --> 0:18:22.560000
 Set dump detail.

0:18:22.560000 --> 0:18:25.320000
 That's like an IP packet detail.

0:18:25.320000 --> 0:18:33.780000
 All right, now let's
 do that PING again.

0:18:33.780000 --> 0:18:35.540000
 There we go, that's what
 I was looking for.

0:18:35.540000 --> 0:18:38.320000
 Set dump detail is what
 we were looking for.

0:18:38.320000 --> 0:18:41.440000
 So let's go ahead and after our PING
 is done here, which I think it's

0:18:41.440000 --> 0:18:44.480000
 done, set dump off.

0:18:44.480000 --> 0:18:49.480000
 And starting at the top, we can see
 the detail we were looking for.

0:18:49.480000 --> 0:18:52.260000
 So let's go all the way to
 the top of this TCP stream.

0:18:52.260000 --> 0:18:54.800000
 Okay, so here was when
 I did my TCP PING.

0:18:54.800000 --> 0:19:01.480000
 So here we see source address, destination
 address, protocol is TCP, acknowledgement

0:19:01.480000 --> 0:19:03.720000
 number, sequence number, flags.

0:19:03.720000 --> 0:19:04.420000
 This is the sync.

0:19:04.420000 --> 0:19:06.300000
 This is the TCP sync.

0:19:06.300000 --> 0:19:10.040000
 Here's the incoming sync
 ACK and the ACK.

0:19:10.040000 --> 0:19:13.720000
 So right here, these three show me
 all the details of my TCP three way

0:19:13.720000 --> 0:19:18.220000
 handshake. And then we can see the
 push bit and the ACK bit are set.

0:19:18.220000 --> 0:19:20.820000
 So as you can go through this, you
 can get a lot more information than

0:19:20.820000 --> 0:19:24.200000
 you normally could in just
 a regular debug IP packet.

0:19:24.200000 --> 0:19:28.120000
 Within a router, using
 the set dump detail.

0:19:28.120000 --> 0:19:33.240000
 And once again, set dump off was
 the way that you turn it off.

0:19:33.240000 --> 0:19:37.340000
 So there's a lot more that you
 can do with virtual PCs.

0:19:37.340000 --> 0:19:40.920000
 I would encourage you
 to Google VPCS.

0:19:40.920000 --> 0:19:43.260000
 There's a lot of documentation
 out there on it.

0:19:43.260000 --> 0:19:47.320000
 But hopefully in this video, I've given
 you a good starting point as far

0:19:47.320000 --> 0:19:51.120000
 as some good ideas as to ways you can
 use this to test various features

0:19:51.120000 --> 0:19:53.280000
 and protocols in your topology.

