So how did you do? How did you do with the lab?
Hopefully you did. Great.
The more you practice working with any technology,
the better and more comfortable you're going to be with it.
And that equates to actually in production
being more efficient and effective in configuring and off
and troubleshooting when something doesn't go quite right.
So with these tasks in mind,
join me in the walkthrough right now
as we implement these lab tasks
and verify flexible net flow on R2.
So I've taken the liberty of using the reset option here on the lab
and I've restarted it. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and I've restarted it.
So it's going to be back at square one.
And as a reminder, if you're in the middle of a lab
and you something goes wrong
or you just want to start over from scratch,
please feel free to use that reset option
and then restart the lab
and it'll give you a nice fresh start anytime you need it.
And here we go.
So I'm going to go ahead and first of all double click
on the lab topology icon here on the desktop
just so we have it available.
Also, this topology is in the skills.
So if you want to download it from the skill
or put it on a second monitor,
so it's really easy to look at that be good too.
So next, let's go ahead and double click on server one WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So next, let's go ahead and double click on server one
and open that up so we can get to the console access for R2.
And here comes server one.
We'll give that a moment to initialize fantastic.
And then we're also going to need client nugge
to generate some traffic.
So I'm going to go ahead and double click on client nugge as well.
Then I can toggle between them down here from the taskbar.
So this is client nugge and let's go and minimize that
and let's go back to server one.
And here we have the tab for R2 fantastic.
So let me do a quick show flow record.
Make sure I don't have any customized records yet. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Make sure I don't have any customized records yet.
Show flow exporter and show flow monitor and nothing fantastic.
So let's start off by creating our flow record.
So I also have here on this computer on server one.
I've got a little notepad document and it's called net floats
right on the desktop.
If you close this and you need to refine it,
it's on the desktop and this basically has the syntax.
So if you want to peek at this or refer to this,
please feel free to do that.
If I go ahead and make this a little bit smaller and scootch this
over just a little bit and move that over a little bit to the right WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
over just a little bit and move that over a little bit to the right
so we can see both of them at the same time.
So in configuration mode, we'll create our flow record first
and effectively it's going to be these commands right here.
We do the same ones in the demo earlier.
So I'm going to copy those from our text document,
put it in then we can do a do show flow record.
And there's our flow record matching on IPV for source
and destination address and also the IPV for protocol.
And then if we want to, we can also go ahead and add a collect.
So if you're typing collect and space question mark,
we could go ahead and also add other items as well
as far as the information you want to collect.
But for the lab, I just want to match on those three things WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But for the lab, I just want to match on those three things
to identify a flow.
So that's in place.
So our next step is to create our export.
And the reason I'm doing the record first and then the exporter
and then the monitors because the monitor right here includes
pointing to which record we want to use and which exporter we want to use.
So if you don't have them created first, you can't actually include them.
So for our flow exporter, we're going to call it our dash flow dash exporter.
The destinations are server at 23 dot 1 dot 2 dot 100.
Our source is going to be loop back zero and the transport is going to be UDP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Our source is going to be loop back zero and the transport is going to be UDP
port 996.
So I'm going to copy that.
I'm going to exit out of the flow record configuration back to global config
and paste that in and boom.
Now if we do a do show flow exporter and press center,
there's our flow exporter with the destination address,
the port, the source address and that looks good to go.
So next we'll exit out of exporter configuration mode and we'll create our flow
monitor
and the flow monitor is simply going to include the record that we created
earlier
as far as what we want to use and which exporter we want to use. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
as far as what we want to use and which exporter we want to use.
So we'll go ahead and copy that, paste that in.
And now that that's done, we can do a do show flow monitor.
And then once that's done, we do a do show flow monitor just to confirm.
So we do a show flow record show flow exporter show flow monitor just to verify
each of the pieces, which is not a bad idea to do right now.
Before we apply this flow monitor to an interface,
let's do a show flow record that looks good and a show flow exporter.
And that looks good and a show flow monitor and that looks good. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that looks good and a show flow monitor and that looks good.
Great.
So next let's apply this to the three interfaces on our two.
So we're going to configuration mode interface range for gig zero slash zero
and gig one slash zero and gig two slash zero.
And then we'll apply that and let's take a look at the lab task real quick.
They wanted to apply that inbound on those three interfaces.
So we'll do that next.
So the syntax would be IP, hello monitor, a question mark, the name of our
monitor.
So I'll go ahead and also copy paste that so type of space question mark. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I'll go ahead and also copy paste that so type of space question mark.
And we want it for ingress traffic.
So we'll say input and press center boom and we are done.
So now if we did a show flow monitor based question mark and we put the name
of our flow monitor and space question mark and then typing cache,
it'll show us the current cache.
And so currently we have based on protocol UDP that's protocol number 17.
That's UDP traffic going from our client to the server.
Looks like we have some ICMP traffic, which is protocol one going from the
server
to that client. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
to that client.
And then we have protocol 89, which is OSPF.
And because in the record we're using, we didn't ask for information about the
TOS
or the precedence or the TTL that information isn't included because it wasn't
being asked for.
So let's generate some traffic from our Windows client.
So we go down to our Windows client down here.
If it's not open, you just go ahead and open it up with client and I go up at
the top right.
And let's do something that we haven't done previously.
And let's go ahead and ping some remote IP address.
So in the bottom left, we have our Windows client machine. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So in the bottom left, we have our Windows client machine.
Let's go ahead and ping about our fours gig one zero interface address,
which is 1034 zero dot four.
So go ahead and do a ping to 10 dot 34 dot zero dot four press center.
That seems to be working and we'll go back down to server one.
We'll hit the up arrow key and look at the cache again.
And this time we should have that cache.
This time we should have that information.
So there's protocol one from 10, 10, 0, 50 going to 1034, 0, 4.
And there is the reply traffic coming back. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And there is the reply traffic coming back.
And that's because we have the monitor applied to gig one zero and gig zero
zero inbound.
And that's why it's catching both sides of that conversation or in the case of
net flow,
both flows of traffic.
So thanks for joining me in this set of videos and his hands on lab regarding
flexible net flow.
And I look forward to seeing you my friend in a future set of videos very, very
soon.
Until then, I hope this has been informative and I'd like to thank you for
viewing.