WEBVTT

1
00:00.000 --> 00:02.200
For this hands-on lab, here's what I'd like you to do,

2
00:02.200 --> 00:05.480
pretty much mirroring what we did in the videos up to this point.

3
00:05.480 --> 00:06.760
I'd like you to configure NetFlow,

4
00:06.760 --> 00:10.440
flexible NetFlow specifically on R2 using the following.

5
00:10.440 --> 00:13.000
I'd like you to create a flow record called

6
00:13.000 --> 00:17.200
our-flow-record and I want you to match on three things.

7
00:17.200 --> 00:20.760
IPv4 protocol, IPv4 source IP address,

8
00:20.760 --> 00:23.480
and the IPv4 destination IP address.

9
00:23.480 --> 00:25.120
Then once you have that flow record created,

10
00:25.120 --> 00:27.120
I'd like you to create a flow exporter named

11
00:27.120 --> 00:32.440
our-flow-exporter with the destination server of 2312100
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:27.120 --> 00:32.440
our-flow-exporter with the destination server of 2312100

12
00:32.440 --> 00:37.040
and a source of loopback 0 and the UDP destination port of 996.

13
00:37.040 --> 00:39.840
Now, it doesn't matter whether or not we actually have

14
00:39.840 --> 00:43.080
a functional NetFlow collector at that IP address,

15
00:43.080 --> 00:45.560
but I want to make you familiar with how to configure it.

16
00:45.560 --> 00:48.360
The reason I'm doing it in this order is because when we go to

17
00:48.360 --> 00:50.280
the flow monitor, which is our third step,

18
00:50.280 --> 00:51.840
it's going to ask for, "Hey,

19
00:51.840 --> 00:53.960
which flow exporter are we going to use,

20
00:53.960 --> 00:56.200
and which flow records are we going to use?"

21
00:56.200 --> 00:59.920
I'd like you to create that our flow monitor as the third step,

22
00:59.920 --> 01:03.280
including the user-defined exporter and record that we created,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.920 --> 01:03.280
including the user-defined exporter and record that we created,

23
01:03.280 --> 01:06.640
and then apply that inbound on gig 0, 0,

24
01:06.640 --> 01:08.960
gig 1, 0, and then gig 2, 0.

25
01:08.960 --> 01:12.320
Once that's done and you've generated some traffic to go through the network,

26
01:12.320 --> 01:16.000
and a good way to do that is to go to the Windows 11 client-nug machine

27
01:16.000 --> 01:17.040
and just ping, for example,

28
01:17.040 --> 01:20.800
33333 or 4444 or ping the server itself,

29
01:20.800 --> 01:22.680
and the NetFlow cache should show that.

30
01:22.680 --> 01:24.840
To see the NetFlow cache, you just come in and show,

31
01:24.840 --> 01:29.600
"flow monitor", the name of the monitor, and then the keyword cache.

32
01:29.600 --> 01:31.800
And as far as a little bit of help in the lab,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:29.600 --> 01:31.800
And as far as a little bit of help in the lab,

33
01:31.800 --> 01:35.280
there's also a document on Server 1 regarding NetFlow.

34
01:35.280 --> 01:36.280
It's a text document.

35
01:36.280 --> 01:39.560
You can open it up, and that also has the commands to implement this

36
01:39.560 --> 01:42.800
if you need a little bit of help or you want to peek at that configuration.

37
01:42.800 --> 01:44.600
So have some fun with the hands on that,

38
01:44.600 --> 01:47.240
and when you are done with it and ready for a walkthrough,

39
01:47.240 --> 01:49.680
join me in the next video and we'll do that together.